Database Develop

[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

From Lolipop downgrade to Kit Kat (XT1068)

Hello guys. I have a problem to downgrade from Lolipop to Kit Kat stock firmware. I use this link http://forum.xda-developers.com/moto-g-2014/general/how-to-install-lollipop-xt1068-xt1069-t2941349 upgrade to Lolipop. I decide to downgrade to stock firmware Kit Kat. I've been following this link to downgrade http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 but then it says " failed validate image " or something. I use XT1068. I've been try this RETAILDSDSALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC_SVC.xml firmware and this RETAILDSDSALL_XT1068_4.4.4_KXB21.85-27_cid7_CFC_SVC.xml but fail to sucseed. BTW, I live in Malaysia. If you guys found a specific stock firmware Kit Kat link to me, I'm glad you guys help to help me. TQ.

I had this problem with mine I have a UK xt1068 as my boot loader is unlocked it seems to be when you do fastboot OEM lock it fails to validate the image so if you skip the fastboot OEM lock command it should hopefully go back to KitKat hope this makes sense
Sent from my XT1068 using XDA Free mobile app

It works!
hulkbuster92 said:
I had this problem with mine I have a UK xt1068 as my boot loader is unlocked it seems to be when you do fastboot OEM lock it fails to validate the image so if you skip the fastboot OEM lock command it should hopefully go back to KitKat hope this makes sense
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
it works man! TQ! phewwwww! last question. how to relocked the bootloader?

I don't know as I haven't relocked it I will try and see if I can lock it using the stock firmware for my required phone
UPDATE I tried to relock the bootloader using the original stock firmware but it was unsuccessful
Sent from my XT1068 using XDA Free mobile app

Nothing works for me though!
I tried everything. Skipped the command, tried to flash 5.0.2 XT1068 boot.img and recovery,img but none of them fail, All I get is some sort of error - "Preflash Validation Failed" "Failed to erase partition" . . . .
Bootloader also shows Device is Unlocked but I don't get the "warning device is unlocked" message. Strange isn't it?
Any help?

adityasam said:
I tried everything. Skipped the command, tried to flash 5.0.2 XT1068 boot.img and recovery,img but none of them fail, All I get is some sort of error - "Preflash Validation Failed" "Failed to erase partition" . . . .
Bootloader also shows Device is Unlocked but I don't get the "warning device is unlocked" message. Strange isn't it?
Any help?
Click to expand...
Click to collapse
trying using the version in my signature - save to pc / unzip read instructions

reefuge said:
trying using the version in my signature - save to pc / unzip read instructions
Click to expand...
Click to collapse
Very sorry but the exact same errors persist. I can't understand the problem first, seems like a corrupt bootloader that won't accept anything. Nor am I sure the bootloader is unlocked. I don't get the warning message but my bootloader says it is.
Thanks for your time in any case!

xt1068 kitkat rom is not loading in my phone
i tried moreless all roms but still my phone on 5.0.2
plz help

XT1060 Weird Build Version

I have been attempting to revert my rooted XT1060 but am having trouble reverting recovery. I then noticed my build version was odd, and can't find it anywhere online:
Blur_Version.213.46.1.ghost_verizon.Verizon.en.US
My build ID is still: KXA21.12-L1.26.1
Kernel is: 3.4.42-gb278d02 (can't find that anywhere also)
Has anyone seen this build version before? I'm wondering if I did something screwy when I unlocked and flashed twrp originally....

I just reverted my Dev edition back to stock in anticipation of the 5.1 OTA. I used the firmware file I got directly from Motorola last fall. Flashed it manually using mfastboot. I now have exactly what you have.
213.46.1.ghost_verizon.Verizon.en.US
KXA21.12-L1.26.1
3.4.42-gb278d02
It's not just you!

How strange! And unfortunate since this got me kicked out of the soak test...
Is there a way to read the version numbers from the img/etc files?
My phone appears to function entirely ok so maybe this is just a build number screw up on the moto files?

killsforpie said:
How strange! And unfortunate since this got me kicked out of the soak test...
Is there a way to read the version numbers from the img/etc files?
My phone appears to function entirely ok so maybe this is just a build number screw up on the moto files?
Click to expand...
Click to collapse
It's not giving me the current OTA either. I have no idea how to read version numbers from the files. My phone works perfectly too.
No clue if I've/we've done good or totally screwed ourselves!

My phone works perfectly too.
Click to expand...
Click to collapse
I should mention my recovery is jacked up. I just get the red triangle exclamation mark. I've flashed the stock recovery a few times but same result.
I also downloaded the firmware from Motorola at the beginning of the year but the one I actually flashed I had downloaded this week. The MD5s are the same for both. I'd find it a bit hard to believe there isn't more buzz if this is indeed the case for the firmware from moto for so long.
Can anyone confirm they successfully flashed stock firmware from Motorola within the last 6 months and got the correct build version (212.55.26) and not (213.46.1) from here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images

Install Motorola Device Manager on your computer, put your phone in bootloader mode, connect it to your computer and start MDM - see what MDM says about your firmware.

JulesJam said:
Install Motorola Device Manager on your computer, put your phone in bootloader mode, connect it to your computer and start MDM - see what MDM says about your firmware.
Click to expand...
Click to collapse
Is there a Linux client? I am Windowless.

killsforpie said:
Is there a Linux client? I am Windowless.
Click to expand...
Click to collapse
no just windows and mac os.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

JulesJam said:
no just windows and mac os.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Click to expand...
Click to collapse
Will it tell me more than "fastboot getvar all" will?

killsforpie said:
Will it tell me more than "fastboot getvar all" will?
Click to expand...
Click to collapse
It looks at your version of your system and decides if you are up to date or eligible for an upgrade and then gives you a message about that. It will also say unknown system version or something like that if it doesn't recognize your system version.

I got the same thing when I flashed from the recovery image today. Was marked as VZW_212.55.26.ghost_verizon.Verizon.en.US but installed 213.46.1.ghost_verizon.Verizon.en.US
I ran MDM both in bootloader mode and with my phone up, said current version was N/A
(bootloader) reason: Reboot to bootloader
(bootloader) ro.build.date: Sat Aug 23 00:29:00 PDT 2014
(bootloader) ro.build.id: KXA21.12-L1.26.1
(bootloader) ro.build.tags: release-keys
(bootloader) ro.build.type: user
(bootloader) ro.build.user: dbbuild
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 1
(bootloader) ro.build.version.release: 4.4.4
(bootloader) ro.mot.build.customerid: verizon
(bootloader) ro.product.name: ghost_verizon
(bootloader) ro.build.fingerprint[0]: motorola/ghost_verizon/ghost:4.4
(bootloader) ro.build.fingerprint[1]: .4/KXA21.12-L1.26.1/1:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.213.46.1.ghost_veri
(bootloader) ro.build.version.full[1]: zon.Verizon.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-gb444bf1-00
(bootloader) kernel.version[1]: 004-g6b785f7 ([email protected]
(bootloader) kernel.version[2]: id25) (gcc version 4.7 (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed Jun 25 00:58:4
(bootloader) kernel.version[4]: 2 PDT 2014
Click to expand...
Click to collapse

Can you boot into recovery?

Yes, I can boot into recovery. Since I dead ended with this last night, I reflashed TWRP as well. I haven't been having any problems on this build so far, and it could be a placebo, but it feels like it's running better at least for now.
I did find something else though, this might be the build for the XT1053, or at least the versioning in the file might say it is.
http://forum.xda-developers.com/moto-x/general/xt1053-4-4-4-ota-update-zip-t2885484

I just flashed recovery acquired from Motorola and I also have this weird 213 version on my phone. What gives, what is it? I flashed so I could receive that bug fix OTA but now it doesn't appear anymore.
I don't remember what we had before, but scanning the binary's does match 213, so its definitely a part of system.img:
Code:
[email protected]:~/Downloads/VZW_212.55.26.ghost_verizon.Verizon.en.US$ grep -F '213.46.1.ghost_verizon' *
grep: Darwin: Is a directory
grep: Linux: Is a directory
Binary file system.img matches <--------
grep: Windows: Is a directory
$:~/Downloads/VZW_212.55.26.ghost_verizon.Verizon.en.US$ grep -F '212.166.3.ghost_verizon' *
grep: Darwin: Is a directory
grep: Linux: Is a directory
grep: Windows: Is a directory
$ :~/Downloads/VZW_212.55.26.ghost_verizon.Verizon.en.US$

Oh good work. That definitely looks like it's a problem with the recovery files from moto then. There's a thread on the moto forums I'll post that info to.
https://forums.motorola.com/posts/fe85422acc

Did a little bit of testing on my 2013 Verizon Dev Ed Moto X tonight and I too had installed the 4.4.4 system image from the Moto website a while back and had the same weird build info. I have several 2013 Moto X's in my possession, some unlocked and some not, all received notification of the newest Verizon update except for my Dev Ed Moto X due to this weird system build info. I flashed 4.4.4 on the Dev Ed tonight and had the same weird build version yet again and the newest update would not show for me. I then grabbed the 4.4.2 system image from the Moto website and flashed that image. After flashing, the phone alerted me on boot to the 4.4.4 update. After installing 4.4.4. I was then notified on boot of the newest update released by Verizon and was able to install that successfully. I am now on the latest CORRECT build version. Just thought I would post this info in case it someone finds it useful. I know it doesn't correct the problem with the 4.4.4 factory image but at least it is a path to obtain the newest Verizon updates for those with the weird build info like myself.

xda_fiend said:
Did a little bit of testing on my 2013 Verizon Dev Ed Moto X tonight and I too had installed the 4.4.4 system image from the Moto website a while back and had the same weird build info. I have several 2013 Moto X's in my possession, some unlocked and some not, all received notification of the newest Verizon update except for my Dev Ed Moto X due to this weird system build info. I flashed 4.4.4 on the Dev Ed tonight and had the same weird build version yet again and the newest update would not show for me. I then grabbed the 4.4.2 system image from the Moto website and flashed that image. After flashing, the phone alerted me on boot to the 4.4.4 update. After installing 4.4.4. I was then notified on boot of the newest update released by Verizon and was able to install that successfully. I am now on the latest CORRECT build version. Just thought I would post this info in case it someone finds it useful. I know it doesn't correct the problem with the 4.4.4 factory image but at least it is a path to obtain the newest Verizon updates for those with the weird build info like myself.
Click to expand...
Click to collapse
Good stuff. Now, is there someone directly at motorola we can reach out to to see what's up with the images? I mean, is it possible it's purposefully a newer version so that we have to wait for a different update? It's odd the numbering is off from the package name...

xda_fiend said:
Did a little bit of testing on my 2013 Verizon Dev Ed Moto X tonight and I too had installed the 4.4.4 system image from the Moto website a while back and had the same weird build info. I have several 2013 Moto X's in my possession, some unlocked and some not, all received notification of the newest Verizon update except for my Dev Ed Moto X due to this weird system build info. I flashed 4.4.4 on the Dev Ed tonight and had the same weird build version yet again and the newest update would not show for me. I then grabbed the 4.4.2 system image from the Moto website and flashed that image. After flashing, the phone alerted me on boot to the 4.4.4 update. After installing 4.4.4. I was then notified on boot of the newest update released by Verizon and was able to install that successfully. I am now on the latest CORRECT build version. Just thought I would post this info in case it someone finds it useful. I know it doesn't correct the problem with the 4.4.4 factory image but at least it is a path to obtain the newest Verizon updates for those with the weird build info like myself.
Click to expand...
Click to collapse
The 4.4.4 image on filefactory.com -> http://www.filefactory.com/file/38q6rpe04nov/VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip still works and is also the same "pre-maintenance" version... so flashing it will get you back to the "stock" path.
But yeah, Moto should have the CORRECT version up there on their site.

I thought downgrading was a big no no. Is that only the bootloader?

killsforpie said:
I thought downgrading was a big no no. Is that only the bootloader?
Click to expand...
Click to collapse
It usually is a bad idea...
That being said, there are the rare exception where it has worked for some, then others try it, and it bricks them. So downgrading is really taking a chance.
Also consider if this weird 213.46.1 version has the same bootloader version as the 212.55.26 Android 4.4.4 or the maintenance release 212.166.3 Android 4.4.4 (which we don't have an SBF of), and you don't get an error about GPT.BIN when trying to flash, you should be pretty safe.

Moto X XT1053 stock firmware

Is there anywhere around to still get the stock firmware files for this device?
all of the sites to download the firmware I'm finding on every tutorial and on xda seem to down.

movielover76 said:
Is there anywhere around to still get the stock firmware files for this device?
all of the sites to download the firmware I'm finding on every tutorial and on xda seem to down.
Click to expand...
Click to collapse
Havent found that still?

Salik Iqbal said:
Havent found that still?
Click to expand...
Click to collapse
Nope

movielover76 said:
Nope
Click to expand...
Click to collapse
Check inbox

Salik - I'm also looking for this, can you hook me up? Thx!

movielover76 said:
Is there anywhere around to still get the stock firmware files for this device?
all of the sites to download the firmware I'm finding on every tutorial and on xda seem to down.
Click to expand...
Click to collapse
try links in my
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my KFFOWI using XDA Labs

First off, thanks! - I tried flashing 5.1 using RSD Lite 6.2.4 after updating the latest drivers and following the instructions here: http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
I'm still getting flash fails:
- downgraded security version
- upgrade gpt_main version failed
- preflash validation failed for GPT
In other, older firmwares' xml files I found more of the lines you mention removing in the file prior to flashing but in the TMO XT1053 5 .1 Ghost Retail, there's only the one referring to the max download size.
Upon attempt to flash 4.4.4 I was able to get rid of the preflash validation warning but got (downgraded security version & update sbl3 version failed). I further researched this problem and also re-flashed stock recovery but to no avail. (Bootloader is unlocked BTW - at least fastboot & bootscreen say so)
At this point, I'm out of options - any other tips you could give me?

getdealtwith99 said:
First off, thanks! - I tried flashing 5.1 using RSD Lite 6.2.4 after updating the latest drivers and following the instructions here: http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
I'm still getting flash fails:
- downgraded security version
- upgrade gpt_main version failed
- preflash validation failed for GPT
In other, older firmwares' xml files I found more of the lines you mention removing in the file prior to flashing but in the TMO XT1053 5 .1 Ghost Retail, there's only the one referring to the max download size.
Upon attempt to flash 4.4.4 I was able to get rid of the preflash validation warning but got (downgraded security version & update sbl3 version failed). I further researched this problem and also re-flashed stock recovery but to no avail. (Bootloader is unlocked BTW - at least fastboot & bootscreen say so)
At this point, I'm out of options - any other tips you could give me?
Click to expand...
Click to collapse
you cannot downgrade stock firmware unless bootloader is unlocked
Sent from my XT1080 using XDA Labs

sd_shadow said:
you cannot downgrade stock firmware unless bootloader is unlocked
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
As mentioned, bootloader is unlocked - at least per fastboot & the bootscreen. Are you saying that that might be wrong and that the errors RSD Lite is giving me indicate that the bootloader is locked? Thx

getdealtwith99 said:
As mentioned, bootloader is unlocked - at least per fastboot & the bootscreen. Are you saying that that might be wrong and that the errors RSD Lite is giving me indicate that the bootloader is locked? Thx
Click to expand...
Click to collapse
try mfastboot
Sent from my KFFOWI using XDA Labs

Issue with updating

Hello,
I need support here I purchased my phone from eBay and the seller changed the language and install play Store for me ,now I tried to update the device to last firmware but its give me no update available .
I look into these issue and downloaded the firmware manually give another message that Can't verify update
So please if any one can help me here thanks

didmytime said:
Hello,
I need support here I purchased my phone from eBay and the seller changed the language and install play Store for me ,now I tried to update the device to last firmware but its give me no update available .
I look into these issue and downloaded the firmware manually give another message that Can't verify update
So please if any one can help me here thanks
Click to expand...
Click to collapse
how you updating.
Boot loader is unlocked out of the box probably that's why you can't update.

didmytime said:
Hello,
I need support here I purchased my phone from eBay and the seller changed the language and install play Store for me ,now I tried to update the device to last firmware but its give me no update available .
I look into these issue and downloaded the firmware manually give another message that Can't verify update
So please if any one can help me here thanks
Click to expand...
Click to collapse
What software version are you using?

riz157 said:
how you updating.
Boot loader is unlocked out of the box probably that's why you can't update.
Click to expand...
Click to collapse
So how can I fix that ?

whatwhat1 said:
What software version are you using?
Click to expand...
Click to collapse
8.0.7.0.0

didmytime said:
8.0.7.0.0
Click to expand...
Click to collapse
Same version as me. You have a vendor ROM and not the official ROM installed on your phone. I don't know how to check if the bootloader is locked/unlocked.

I've got 8.0.10.0 (mahcndi)
What does that mean?
What's the difference between vendor Rom & official Rom?

whatwhat1 said:
......I don't know how to check if the bootloader is locked/unlocked.
Click to expand...
Click to collapse
Check out this post:
http://en.miui.com/thread-279195-1-1.html

Forgive me for my noobiness here but now I am worried. If I have the 8.0.7.0 mahcndi does this mean I will not get the official updates or any updates at all? When it's an official rom do they still come ota even if I'm in Canada for example.
Thanks in advance

imapfsr said:
Forgive me for my noobiness here but now I am worried. If I have the 8.0.7.0 mahcndi does this mean I will not get the official updates or any updates at all? When it's an official rom do they still come ota even if I'm in Canada for example.
Thanks in advance
Click to expand...
Click to collapse
Do you have 8.0.7.0 or 8.0.7.0.0? If you have the latter one, then you will not get updates.

whatwhat1 said:
Do you have 8.0.7.0 or 8.0.7.0.0? If you have the latter one, then you will not get updates.
Click to expand...
Click to collapse
Thanks whatwhat,
So it seems I have the double 0 so that sucks. Do you mind if I ask what I need to do to get this phone on a version that will give me the updates when they are available. Again, any direction you can provide me would be greatly appreciated.

imapfsr said:
Thanks whatwhat,
So it seems I have the double 0 so that sucks. Do you mind if I ask what I need to do to get this phone on a version that will give me the updates when they are available. Again, any direction you can provide me would be greatly appreciated.
Click to expand...
Click to collapse
You can check if your bootloader is locked or unlocked and that may be preventing it from updating. http://en.miui.com/thread-279195-1-1.html
But you really need to flash the official MIUI ROM to keep things updated.

Shouldn't there be updated versions of these multi-language ROMs we can get and update through the built in updater?
Sent from my Xiaomi Mi Mix using XDA Labs

SWBgHz said:
Shouldn't there be updated versions of these multi-language ROMs we can get and update through the built in updater?
Sent from my Xiaomi Mi Mix using XDA Labs
Click to expand...
Click to collapse
I highly doubt it. Any custom ROM has the same behavior.

I'm in the same situation and am looking for some much needed help: I purchased the Mi Mix and have 8.0.7.0.0 installed. This is all new to me, but this forum has been very helpful, and as I understand this is a vendor ROM and as such I will not be able to get OTA updates. That indeed sucks.
I'm trying to find out what I need to do to my phone on a version that will allow me to receive updates in the future. I've read posts about checking if my bootloader is locked or unlocked, but as I said a lot of that is over my head. Does anyone have some advice, "101" type help that they can provide?
Can I simply download the Stable ROM 8.0.8.0 (or even 8.0.12.0), copy to my phone, run MIUI8 and select the update package?
Surely its not that easy?
ADB, Fastboot, etc.. its all new to me. I would appreciate any assistance. Thanks!

Unlocked bootloader won't stop updates just vendor rom. you are right it's not that easy follow the guides in the guide section.

still stuck on 8.0.7.0.0 and this is what adb tells me:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.055s]
finished. total time: 0.057s
Thats greek to me.
Is that good / bad?
Can anyone point me to a specific URL with step by step instructions to get this off the vendor rom and onto something updatable?
TIA

favsob said:
still stuck on 8.0.7.0.0 and this is what adb tells me:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.055s]
finished. total time: 0.057s
Thats greek to me.
Is that good / bad?
Can anyone point me to a specific URL with step by step instructions to get this off the vendor rom and onto something updatable?
TIA
Click to expand...
Click to collapse
your device is already unlocked. go to the thread with step by step instructions on how to flash any rom you want and load TWRP.
https://forum.xda-developers.com/mi-mix/how-to/guide-flash-global-china-rom-root-gapps-t3510592