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.

Rogers Moto X 1053 Unlocked bootloader - how return to stock ?

Hi all, sorry if this has been asked before..
I didn't know that kit kat 4.4.2. cannot be rooted lol, so I unlocked my boot loader and spent hours trying to load recovery (TWRP or CWM), obviously with no luck.i saw something online that said 4.4 and I assumed it was good for 4.4.2. Didn't work anyways.
Is there any way to load the factory Rogers rom back on so that I don't have that unlocked bootloaeer warning on every boot ?
If yes, any idea where I can download ??
Also, will this change my status on fast boot to Locked ?
I was so looking forward to setup recovery and root, oh well, I still love the device and will be ok at stock until a fix comes out.
Any help would be very much appreciated
Thanks so much

I don't have time to give extreme details but maybe I can still help point you in the right direction.
First off the Rogers Moto X is an XT1058, not an XT1053.
Once the bootloader is unlocked you can easily root the phone with twrp - same version is used for 4.4 and 4.4.2
You can relock the bootloader but the warning is technically always present. You can overwrite the image with a different one though.
The factory firmware is available for download, you can flash it yourself with rsdlite.
There are easy to find threads with all of the details needed to restore to 100% stock or root the Moto X. A few minutes searching and you should find them. Give it a shot, if after that you have further questions by all means please ask.

Hi, thanks for the reply
You are correct, its a 1058 and I officially unlocked my bootloader with motorola and voided my warranty...
I used this link
http://dottech.org/147327/how-to-root-moto-x-on-android-4-4-kitkat-guide/a
And when I try to install the recovery in terminal, it says (bootloader) variable not supported)
It then says writing recovery, finished (so it seems to write it), but I follow instructions, then reboot using terminal command "fastboot reboot" and try to boot into recovery but its blank.I even tried just rebooting to recovery and it still didnt work...
Or it just reverts to stock boot up.
I have tried others also but cannot seem to get it working properly.
Any chance you can guide me though it ? I would really appreciate it...

Hi I did some searching and got it figured out
Thanks again for your help

Hi again,
For some reason, when I went to reboot this morning, TWRP is gone. I boot into recovery and blank screen, seems it didnt hold.
Any idea why ??
Thanks
Steve-x said:
I don't have time to give extreme details but maybe I can still help point you in the right direction.
First off the Rogers Moto X is an XT1058, not an XT1053.
Once the bootloader is unlocked you can easily root the phone with twrp - same version is used for 4.4 and 4.4.2
You can relock the bootloader but the warning is technically always present. You can overwrite the image with a different one though.
The factory firmware is available for download, you can flash it yourself with rsdlite.
There are easy to find threads with all of the details needed to restore to 100% stock or root the Moto X. A few minutes searching and you should find them. Give it a shot, if after that you have further questions by all means please ask.
Click to expand...
Click to collapse

[Q] Please help in unbricking Atrix HD MB886

Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?

capricorn85 said:
Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?
Click to expand...
Click to collapse
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.

skeevydude said:
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.
Click to expand...
Click to collapse
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......

capricorn85 said:
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......
Click to expand...
Click to collapse
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).

skeevydude said:
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).
Click to expand...
Click to collapse
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...

capricorn85 said:
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...
Click to expand...
Click to collapse
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.

skeevydude said:
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.
Click to expand...
Click to collapse
Came here after trying all that
Tried manually flashing but the phone returns FAIL on EVERY command, same with myth tools it executes but nothing really happen in the phone, dont know what went so wrong with the OTA
i am just confused if i should let it be or keep trying until i find a solution
COuld battery charge level be the problem, when it all started it was more than 70 percent and i didnt keep it on for long. it says battery ok but dont know whats the exact battery level as fastboot oem battery-status or voltage level are also restricted

Well, it seems that skeevydude told you all I want to say

Solved: Using Nextel (Mex Retail)
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue

capricorn85 said:
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue
Click to expand...
Click to collapse
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?

palmbeach05 said:
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?
Click to expand...
Click to collapse
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion

capricorn85 said:
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion
Click to expand...
Click to collapse
I told ya Mex Retail would work....

skeevydude said:
I told ya Mex Retail would work....
Click to expand...
Click to collapse
It is worth a shot for me too!
I have RSDLite and attempted to flash. It gives me error about unknown <getvar>. Deleted those line(s) according to another post I found.
Then everything passes but I am stuck on the Fastboot Flash Mode?
God I will be happy when uncle same gets through with my son so he can help is ole man, lol.
---------- Post added at 06:14 PM ---------- Previous post was at 05:55 PM ----------
PROGRESS! I recalled skeevydude saying to stay alway from front USB ports and moved to back one and I now also have the Mex Retail version working. What a relief.
Now the bearing question is should I move on to another version like carbon or holoblur?
If ok to stay with this version, meaning will NOT get busted out by AT&T by using hotspot?
What do you recommend skeevydude?
Thank you so so so much.
Woody

Mexico Retail link
can someone provide me any link of Mexico Retail stock rom? Please.

ErickST18 said:
can someone provide me any link of Mexico Retail stock rom? Please.
Click to expand...
Click to collapse
http://sbf.droid-developers.org/phone.php?device=7

quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Thanks man

Pleas hlep me for alive my set thanks advance
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English

shamshadhashmi said:
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English
Click to expand...
Click to collapse
Please stop whining and being pathetic and actually search for moto sbf files. A new site popped up and comes up very easily. No need to make us die of laughter at someone begging for an sbf like a guy begging to get with a girl b/c he's thirsty. Smh lol
Sent from my ATRIX HD using XDA Free mobile app

need working link of file
i search everywhere but no file found i need file if anybody have so please share with me or upload thanks

quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Need 4.1.1..where can I find it? Tyvm

[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

Help on XT1254 OTA

Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!

mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
me too
i updated to 6.0.1 via recovery with update.zip. This process had successfully done and re-updated via recovery again (still the same update.zip) and i factory reset tin recovery so it stuck screen 'erasing...'They could not enter system, except bootloader and recovery vesersion (6.0.1),can not into apply update sdcard , it turn e:\unkown volum path [sdcard]... and I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?

longbin said:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Click to expand...
Click to collapse
1. I have never heard of anyone selling bootloader unlock keys for the XT1254. If you want to unlock your bootloader, Sunshine is your only option, and as of right now it will only work on lollipop builds. If your phone is on marshmallow, Sunshine will not work. If your phone cannot boot, it won't work no matter what build you're on.
2. If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.

mr_5kool said:
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
unlock the bootloader and install TWRP BEFORE doing any updates, while still on Lollipop. That is the only safe, logical answer. An unlocked bootloader -- especially with custom recovery -- will let you do lot of things and is more forgiving of mistakes than a locked bootloader.
We keep telling people that and they won't believe us.
---------- Post added at 10:37 AM ---------- Previous post was at 10:32 AM ----------
TheSt33v said:
If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.
Click to expand...
Click to collapse
Right. Several people who didn't like Lollipop but preferred the original Kitkat "speed", "battery life" or whatever successfully downgraded back to 4.4.4 -- but only AFTER they unlocked their bootloader. Even then you have to make sure you don't flash the old gpt.bin in ADB, but downgrading is possible with an UNlocked bootloader.
Even when flashing XT1250 firmware over XT1254 or vice versa, it CAN be done with a locked bootloader, but if you mess something up you are in big trouble. UNlocked bootloader? Just do it again, correcting your mistake the next time.
---------- Post added at 10:43 AM ---------- Previous post was at 10:37 AM ----------
TheSt33v said:
1. I have never heard of anyone selling bootloader unlock keys for the XT1254.
Click to expand...
Click to collapse
There was a guy on some website who was selling some Verizon keys a long time ago, known as "the Chinaman". He disappeared.
China Middleman Back??
http://forum.xda-developers.com/moto-x/moto-x-qa/china-middleman-t2751177
dschill said:
Well the china man added me back on skype today. And sadly said that he can no longer get the codes and refunded my 45$ via paypal.
Heres a little bit of the skype transcipt
[12:08:22 PM] live:dschillinrecovery: k i just got the refund
[12:08:25 PM] live:dschillinrecovery: so you cant get the code any more?
[12:12:41 PM] VIP-UNLOCK: No time to deal with the accident, we default to a refund
[12:13:08 PM] VIP-UNLOCK: Sorry, goodbye
[12:13:32 PM] live:dschillinrecovery: Its alright. Thanks for the refund though. Let me know if you can ever get the codes again
Guess the best we can do for now is to wait for jcase and sunshine to release the 3.0 version.
Click to expand...
Click to collapse
and another thread discussing same guy:
http://forum.xda-developers.com/moto-x/general/4-1-vzw-att-moto-maker-bootloader-t2680651
The process seems to involve sending approximately $45 to a Chinese middle-man via eBay and another website, along with your IMEI and cell phone number, and you will receive an unlock code.
It seems like this is all one guy handling this process. Turnaround time seems to be 24-48 hours beginning to end.
Click to expand...
Click to collapse
Theory was that someone with access to Motorola's engineering software had a side business going. You know they unlock their bootloaders for testing and such. Someone with access to that software could make some money if they made sure they covered their tracks.
Also people who visited China were able to buy unlocked bootloader Droid Turbos well before Sunshine was released. One guy posted in this forum. In that case, it was probably pilfering some phones from the factory -- but again with unlocked bootloaders. So, there is some software out there somewhere, just kept under wraps.

Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.

TheSt33v said:
Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.
Click to expand...
Click to collapse
I updated my post to include XDA links. I can't find any examples of Droid Turbos being unlocked via this eBay "purchase" only other Verizon phones, but there are the legitimate reports of unlocked Droid Turbos for sale in China in the year prior to Sunshine being released November 2015. One guy even posted on here because he was trying to install CM12.1 at the time on his BOOTLOADER UNLOCKED Droid Turbo he had purchased in China.
Note the Chinese middleman guy was charging $45 for bootloader unlock at the time, and Sunshine only charges $25.

xml flash file is the last solution =))

@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250

Doesn anybody know how much does usually takes for Verzion ( or whoever does it ) to release xml sbf firmware file? And do they release every? I need latest MCG24 or at least system file (s) is enough.
I have everything except system files, if anybody can provide system files or knows hot to convert ones from ota , I can make complete fastboot xml zip.
EDIT: System from OTA is not enough. If somebody can provide system / backup from MCG24 phone, I might be able to make it.

mr_5kool said:
@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250
Click to expand...
Click to collapse
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.

ChazzMatt said:
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.
Click to expand...
Click to collapse
Can you give little more info on this. Changed cid? Unlocked bootloader? Maybe we can use x1250 xml fastboot files until they release Marshmallow fastboot. I need one for backup , I know I'll brick the phone sooner or later , as guys above did lol..

Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
Flashed the Verizon radio and 5.1 FW (firmware)
The only problem I have right now is upload speeds are super slow.
gonna try wiping the radio and re-writing the radio
Click to expand...
Click to collapse
I then asked him a couple of questions and he answered this:
Yes I flashed the Verizon Radio to the device
not the bootloader image, for obvious reasons
I wanted 5.1, so I didn't test until I had the VZW 5.1 with my SIM card
I'm going to try an reflash soon, and then get a new SIM just in case
I hope Verizon doesn't give me any trouble getting a new SIM at my local store
Click to expand...
Click to collapse
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.

ChazzMatt said:
Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
I then asked him a couple of questions and he answered this:
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.
Click to expand...
Click to collapse
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..

Ej?iSixo said:
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..
Click to expand...
Click to collapse
That's been done, too. I didn't know that was the question.
One guy didn't want Verizon bloatware and his solution was to flash the "pure" Motorola firmware from the XT1250 over his XT1254.
Yes, he had unlocked bootloader and could have just uninstalled the bloatware. I'm not saying it was logical, I'm just telling you what he did.
So there's no question these two phones are exactly the same device, with exactly the same FCC ID.
The issue is the XT1250/XT1254 being flashed needs to the other needs an unlocked bootloader. And you can't downgrade (gpt.bin) when you flash.
So, for the purposes of this thread that information doesn't help you, if your XT1254 bootloader isn't unlocked.

mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
Conclusion: Wait for the 6.0.1 flash file (xml) then flash via RSD.
Thanks guys!!!!
Click to expand...
Click to collapse
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571