Database Develop

No OTAs on AT&T XT1058

Hi, I just bought a used Moto X (2013). There is no carrier branding on the back and it's written Xt1058 but the ROM installed is of AT&T. When I installed WhatsApp, it said that my phone has a 'custom ROM' and that some features won't work, but otherwise the phone is working just fine. Due to this ROM I'm not getting OTAs as well and I'm stuck on 4.2.2 Jellybean.
My question is that can I flash any other ROM on the phone so that I start receiving OTAs and while making sure that my phone remains unlocked? I don't want to end up locking my phone again. Can flashing a new ROM lock my phone again? Can I revert to stock ROM somehow (maybe the set isn't originally of AT&T)? Or can I flash Rogers ROM which also of XT1058?
In need of help. Thanks.

Flashing a ROM will not lock your bootloader.
You can only flash same firmware versions or newer, never downgrade.
Yes you can flash the stock Rogers firmware. You can find it in the going back to stock guide.

nhizzat said:
Flashing a ROM will not lock your bootloader.
You can only flash same firmware versions or newer, never downgrade.
Yes you can flash the stock Rogers firmware. You can find it in the going back to stock guide.
Click to expand...
Click to collapse
Thanks. Sorry for bothering but I meant SIM locking. Will flashing a ROM SIM lock my phone again or is the answer still the same?
Secondly, how would I know which is the stock ROM for me? It says XT1058 and 'Assembled in China' on the back, so maybe it's from some Latin American country. Should I still go for the Rogers ROM because it's bloat-free?

RafaySid said:
Thanks. Sorry for bothering but I meant SIM locking. Will flashing a ROM SIM lock my phone again or is the answer still the same?
Click to expand...
Click to collapse
It will not SIM lock your phone.
RafaySid said:
Secondly, how would I know which is the stock ROM for me? It says XT1058 and 'Assembled in China' on the back, so maybe it's from some Latin American country. Should I still go for the Rogers ROM because it's bloat-free?
Click to expand...
Click to collapse
Since your phone has already been Bootloader unlocked (because the ROM in your phone is not stock right now), it doesn't matter which ROM you choose. I'd say choosing a bloat-free ROM is great!

RafaySid said:
Hi, I just bought a used Moto X (2013). There is no carrier branding on the back and it's written Xt1058 but the ROM installed is of AT&T. When I installed WhatsApp, it said that my phone has a 'custom ROM' and that some features won't work, but otherwise the phone is working just fine. Due to this ROM I'm not getting OTAs as well and I'm stuck on 4.2.2 Jellybean.
My question is that can I flash any other ROM on the phone so that I start receiving OTAs and while making sure that my phone remains unlocked? I don't want to end up locking my phone again. Can flashing a new ROM lock my phone again? Can I revert to stock ROM somehow (maybe the set isn't originally of AT&T)? Or can I flash Rogers ROM which also of XT1058?
In need of help. Thanks.
Click to expand...
Click to collapse
First you need to know if your bootloader is unlocked or locked.
Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says for the following...
(bootloader) version-bootloader:
(bootloader) revision-hardware:
(bootloader) unlocked:
(bootloader) sku:
(bootloader) cid:
(bootloader) ro.build.id:
(bootloader) ro.build.fingerprint[0]:
(bootloader) ro.build.fingerprint[1]:
(bootloader) ro.build.version.full[0]:
(bootloader) ro.build.version.full[1]:
(or copy/paste the entire output into a post and I'll pick it out).
If the bootloader is locked, you'll only be able to flash Stock ROMs signed by Moto, and made for the same "(bootloader) cid:" as your phone.
Flashing a ROM will not lock a bootloader that has been unlocked. The only time I've seen flashing a ROM re-sim lock is the Sprint XT1056 where a hack is used to sim unlock it.
Btw, ATT phones usually have the ATT carrier branding on the case, even if it was from Moto Maker.

KidJoe said:
First you need to know if your bootloader is unlocked or locked.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says for the following...
(bootloader) version-bootloader:
(bootloader) revision-hardware:
(bootloader) unlocked:
(bootloader) sku:
(bootloader) cid:
(bootloader) ro.build.id:
(bootloader) ro.build.fingerprint[0]:
(bootloader) ro.build.fingerprint[1]:
(bootloader) ro.build.version.full[0]:
(bootloader) ro.build.version.full[1]:
(or copy/paste the entire output into a post and I'll pick it out).
If the bootloader is locked, you'll only be able to flash Stock ROMs signed by Moto, and made for the same "(bootloader) cid:" as your phone.
Flashing a ROM will not lock a bootloader that has been unlocked. The only time I've seen flashing a ROM re-sim lock is the Sprint XT1056 where a hack is used to sim unlock it.
Btw, ATT phones usually have the ATT carrier branding on the case, even if it was from Moto Maker.
Click to expand...
Click to collapse
2nd line: 30.70 (sha-88483d6, 2013-07-02 15:32:03)
.
.
.
.
Device is UNLOCKED. Status Code: 1
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Farooq>cd/
C:\>cd android
C:\Android>fastboot getvar all
(bootloader) version-bootloader: 3070
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Hynix S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x8300
(bootloader) radio: 0x1
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: TA1760BS0H
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: EF8D10040C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Key pressed
(bootloader) ro.build.date: Fri Jul 12 11:37:14 CDT 2013
(bootloader) ro.build.id: 13.9.0Q2.X_140
(bootloader) ro.build.tags: intcfg,test-keys
(bootloader) ro.build.type: userdebug
(bootloader) ro.build.user: e13522
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 23546373
(bootloader) ro.build.version.release: 4.2.2
(bootloader) ro.mot.build.customerid: att
(bootloader) ro.product.name: ghost_att
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.2.2/1
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X_140/23546373:userdebug
(bootloader) ro.build.fingerprint[2]: /intcfg,test-keys
(bootloader) ro.build.version.full[0]: Blur_Version.13.0.23546373.ghost
(bootloader) ro.build.version.full[1]: _att.ATT.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-xline-eng-g
(bootloader) kernel.version[1]: 66c71d4 ([email protected])
(bootloader) kernel.version[2]: (gcc version 4.6.x-google 201201
(bootloader) kernel.version[3]: 06 (prerelease) (GCC) ) #1 SMP P
(bootloader) kernel.version[4]: REEMPT Fri Jul 12 11:55:44 CDT 2
(bootloader) kernel.version[5]: 013
all:
finished. total time: 0.122s
C:\Android>

A few things..
With Bootloader of 30.70, that is the initial shipping bootloader. Based on the versions, it appears to also been the initial shipping ATT ROM. (i.e. the previous owner did not flash only PARTS of a ROM).
Unlocked Status 1 is good. You should be able to flash signed and unsigned roms. So if you want to switch to CM or such, you can. And you can flash 3rd party recovery and root too.
A few things that concern me from the fastboot output...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
I've only seen it say YES or NO for those. This is the first I've seen "Not Supported"
(bootloader) cid: 0xdead
I've not seen the CID listed as DEAD before. Its always been a hex value.
And I'm hoping you just removed your imei and meid, and not that they are actually missing from the output.
One last thing I missed in your other posts, that it says XT1058 on the back and MADE IN CHINA. The ATT XT1058's all said made in USA if I'm not mistaken. So chances are best that its NOT an ATT XT1058.
What carrier are you using this phone on? Do they sell the XT1058? If so, consider finding the latest XT1058 SBF for that carrier and flashing it.
RISKS of doing that: It might fail and brick your phone in the process. It might be successful but you end up having no IMEI/MEID in the process. You end up in a state where you have that SBF on there, but improper carrier settings so future OTA's fail and you have to flash them manually. Or Best case.... It works, and those variables go back to "normal" values.
Its your call if you want to take the chance.

Thanks for the kind reply, I really appreciate it.
I asked Motorola's support person on live chat and he said that the previous owner most probably damaged the phone while flashing as it is not showing any IMEI number. I think the previous guy most probably flashed an AT&T ROM on it and this phone is likely to be from Latin America (XT1058). I'm interested in flashing Roger's ROM as it is bloat-free. I won't flash KitKat on it since it has battery draining issues and will wait for Lollipop.
But are the..
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
..things to be worried about? Will I most probably end up bricking it?

RafaySid said:
Thanks for the kind reply, I really appreciate it.
I asked Motorola's support person on live chat and he said that the previous owner most probably damaged the phone while flashing as it is not showing any IMEI number. I think the previous guy most probably flashed an AT&T ROM on it and this phone is likely to be from Latin America (XT1058). I'm interested in flashing Roger's ROM as it is bloat-free. I won't flash KitKat on it since it has battery draining issues and will wait for Lollipop.
Click to expand...
Click to collapse
Yes, definitely caused while screwing around and doing something that shouldn't have been done.
So the IMEI is definitely missing? I would think in that case you wont see the mobile/cellular network and only Wifi would work. But you said other than the OTA's the phone was working fine.
There were some threads about some getting into that situation (Missing IMEI). I know there were some XT1052 users trying to flash Non-XT1052 roms and running into this, but being unable to recovery. I think there was some users who ran into it for other reasons and were able to recover. Its time to start searching. Like -> http://forum.xda-developers.com/moto-x/moto-x-qa/cdn-rogers-1058-fr-4-4-2-update-to-4-4-t2842787
RafaySid said:
But are the..
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
..things to be worried about? Will I most probably end up bricking it?
Click to expand...
Click to collapse
As I've said, the "Not Supported" and "0xdead" values do worry me. I've not seen them before, so I can't tell you what impact they have on flashing. That is why I said bricking was a risk and that its your choice what to do.
At this point, if you have a working phone, keep with it and using it. Or you try and flash a Rogers XT1058 SBF, taking the chance of bricking it in the process. If you take this route, use Option 5 (and its pre-req's) at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html Get roms from places in this thread -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
I would really suggest flashing the LATEST SBF, in this case 4.4.4.
As for the "battery drain" reported under 4.4.4, for me anyway it seems to vary depending on installed apps. I can still get more than a day with my XT1060 running 4.4.4 with all google and moto apps updated. Occasionally after a bunch of apps update, I see less battery life, but then it seems to settle down and go back to normal.
If you want to flash Rogers 4.4.4, per this thread -> http://forum.xda-developers.com/mot...rogers-canada-4-4-4-sbf-t2905525/post56055157 it appears to be XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip BUT I HAVE NOT CONFIRMED THIS SO PROCEED WITH CAUTION!!!
Good Luck!!

The cellular network is working fine. Can I at least root it? Which method should I choose?

RafaySid said:
The cellular network is working fine. Can I at least root it? Which method should I choose?
Click to expand...
Click to collapse
First, find a copy of the SBF for the rom on your phone before you do anything.
Since you have an unlocked bootloader, just follow -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738
Because you have an older rom and bootloader, just use the versions linked in there. If you ever update the ROM on your phone, you would want to consider using newer versions of TWRP and SuperSU

In order to root, do I need a custom recovery? I'm at 4.2.2 Jellybean atm.

In order to root, you need to read. Seriously, just read and you'll have your answer.

I'm being 'extra careful' because of those abnormal values.
Sent from my Moto X using Tapatalk

RafaySid said:
In order to root, do I need a custom recovery? I'm at 4.2.2 Jellybean atm.
Click to expand...
Click to collapse
There are two ways to root one is for LOCKED bootloaders, the other is if your bootloader is UNLOCKED.
Unlocked bootloader is done by flashing a custom recovery like TWRP, rebooting to bootloader (so the recovery sticks), entering the recovery, and TWRP will usually ask you if you want to root so you answer yes. (sometimes manually installing SuperSU from TWRP is needed). This both roots and disables write protection.
For a LOCKED bootloader you are exploiting vulnerabilities in the roms. You need to be on a certain rom for it to work, there are extra hacks needed to disable write protection. Its a complicated process that sometimes requires flashing different roms. (I don't remember back to the original shipping 4.2.2 for locked bootloader process, I think it might be PwnMyMoto??).
Because of those values on your phone, any flashing or hacking could be risky. Doing the unlocked method (thread link I pasted earlier) of flashing twrp, is the easiest way to root.
Unless you are willing to take a chance, and risk bricking your phone, I'm not sure how to really advise you because everything at this point is unknown territory.

KidJoe said:
There are two ways to root one is for LOCKED bootloaders, the other is if your bootloader is UNLOCKED.
Unlocked bootloader is done by flashing a custom recovery like TWRP, rebooting to bootloader (so the recovery sticks), entering the recovery, and TWRP will usually ask you if you want to root so you answer yes. (sometimes manually installing SuperSU from TWRP is needed). This both roots and disables write protection.
For a LOCKED bootloader you are exploiting vulnerabilities in the roms. You need to be on a certain rom for it to work, there are extra hacks needed to disable write protection. Its a complicated process that sometimes requires flashing different roms. (I don't remember back to the original shipping 4.2.2 for locked bootloader process, I think it might be PwnMyMoto??).
Because of those values on your phone, any flashing or hacking could be risky. Doing the unlocked method (thread link I pasted earlier) of flashing twrp, is the easiest way to root.
Unless you are willing to take a chance, and risk bricking your phone, I'm not sure how to really advise you because everything at this point is unknown territory.
Click to expand...
Click to collapse
Yes thank you. I had already rooted using TWRP.

Can I install an offline update instead of flashing, to update 4.2.2?
Sent from my Moto X using Tapatalk

These 2 threads have everything you need to know,
Rooting,
http://forum.xda-developers.com/showthread.php?t=2826159
Flashing firmware, (returning to stock section)
http://forum.xda-developers.com/showthread.php?t=2603358
I'm not sure what you are meaning by "offline" update... But how to update manually is covered in above thread. ?

Yeah I meant manually updating. Thanks.
Sent from my Moto X using Tapatalk

RafaySid said:
Yeah I meant manually updating. Thanks.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
there are two types of Update.
OTA update (they are incremental, only flash what changed since the last version, need to be stock recovery, and rest of phone as close to stock as possible. and you'll need a certain version on your phone)
Flashing a full SBF (as explained earlier when I mentioned about possibly flashing the Rogers XT1058 rom, and pointed you towards using Option 5 and its pre-req's at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html . It has a couple commands repeated which makes it a little more successful. )
Either way, in your situation, is risky.

AT&T XT1058 - Stuck on 4.2.2

Hello,
I just bought a used Moto X (2013). There is no carrier branding on the back and it's written Xt1058 but the ROM installed is of AT&T.
Whenever I try and update click the CHECK FOR UPDATE, it says, " NO UPDATE FOUND " your device is up to date.
The phone is NOT ROOTED as there are no superuser type apps on the phone. Not sure about the bootloader though. Phone runs perfectly fine just this update thing is getting me worried.
Its currently on 4.2.2
Can anybody please tell me why I cant get the OTA or what should I do to update it to KITKAT?
Thank you in advance.

I tried the adb fastboot thing, but it says waiting for device and never shows anything. Does that have anything to do with the phone or the Operating System im using (WINDOWS 8.1)

Please see -> No OTAs on AT&T XT1058
Please do what is listed in Post #5 and post the results. also include what it says for (bootloader) iswarrantyvoid: and who is the carrier you are using it on?

C:\Program Files (x86)\Minimal ADB and Fastboot>
(bootloader) version-bootloader: 3070
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Elpida S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Toshiba REV=06 PRV=00 TY
(bootloader) product: ghost
(bootloader) revision-hardware: 0x81B0
(bootloader) radio: 0x1
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: LXAA1H0042
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: 420E19000C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Reboot to bootloader
(bootloader) ro.build.date: Sat Jul 6 01:51:06
(bootloader) ro.build.id: 13.9.0Q2.X-116-X-17
(bootloader) ro.build.tags: bldacfg,release-keys
(bootloader) ro.build.type: userPAEH\♦☺è
(bootloader) ro.build.user: hudsoncm
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 8
(bootloader) ro.build.version.release: 4.2.2
(bootloader) ro.mot.build.customerid: att
(bootloader) ro.product.name: ghost_att
(bootloader) ro.build.fingerprint[0]: motorola/g
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X-
(bootloader) ro.build.fingerprint[2]: g,release-
(bootloader) ro.build.version.full[0]: Blur_Vers
(bootloader) ro.build.version.full[1]: ATT.en.US
(bootloader) kernel.version[0]: Linux version 3.
(bootloader) kernel.version[1]: 699-00155-g0f202
(bootloader) kernel.version[2]: 3lnxdroid79) (gc
(bootloader) kernel.version[3]: google 20120106
(bootloader) kernel.version[4]: C) ) #1 SMP PREE
(bootloader) kernel.version[5]: :04:24 CDT 2013

I am using wataniya on it. Phone and everything works pretty fine. I am just stuck on 4.2.2. Like the member in the thread you pointed out to.

OmMeE said:
I am using TELENOR on it. Phone and everything works pretty fine. I am just stuck on 4.2.2. Like the member in the thread you pointed out to.
Click to expand...
Click to collapse
And like the member in that other thread... you have...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
were the IMEI and SKU really reported as 0's, or did you do that in your post here to keep them hidden?
Btw, if you follow that other thread, I gave a lot of warnings of the phone being in an unknown state, I wasn't sure if it was safe or not to try and flash, do so at your own risk, etc... in the end, the user flashed the Rogers Canada XT1058 rom -> http://www.filefactory.com/file/5z0...4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip using mFastboot, and did a factory reset. It didn't cure the values I'm pointing out which are not standard.. but it did get him to 4.4.4 and was working on his GSM carrier..
If you're up for it, and are willing to take the risk, maybe that will work for you too... and hopefully it doesn't brick your phone.

KidJoe said:
And like the member in that other thread... you have...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
were the IMEI and SKU really reported as 0's, or did you do that in your post here to keep them hidden?
Btw, if you follow that other thread, I gave a lot of warnings of the phone being in an unknown state, I wasn't sure if it was safe or not to try and flash, do so at your own risk, etc... in the end, the user flashed the Rogers Canada XT1058 rom -> http://www.filefactory.com/file/5z0...4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip using mFastboot, and did a factory reset. It didn't cure the values I'm pointing out which are not standard.. but it did get him to 4.4.4 and was working on his GSM carrier..
If you're up for it, and are willing to take the risk, maybe that will work for you too... and hopefully it doesn't brick your phone.
Click to expand...
Click to collapse
I didnt hide anything, just posted as it came on the CMD.
So if I flash to that rogers rom, will I be getting future updates or will I have to flash everytime?
Also, my apologies, but can you point me towards a step by step guide for using mfastboot, as im new to this and running windows 8.1.

OmMeE said:
I didnt hide anything, just posted as it came on the CMD.
So if I flash to that rogers rom, will I be getting future updates or will I have to flash everytime?
Also, my apologies, but can you point me towards a step by step guide for using mfastboot, as im new to this and running windows 8.1.
Click to expand...
Click to collapse
Ok, well, seeing those things things, let me reiterate that your phone is in an "unknown" or at least "unusual" state. Anything you do at this point is risky! So its up to you if you really want to do anything (like flashing) or leave it like it is (since its working).
There is a chance you will not get updates if you are using the XT1058 rom branded for another carrier. (i.e. if you have the ATT XT1058 rom on an XT1058 being used on a different carrier).
As for step by step... you have a few options..
http://mark.cdmaforums.com/MotoX-ReturnToStock.html See the requirements at the top of the page, and then option 5
Or...
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Oh, and I only suggested the Rogers Canada XT1058 rom because it worked for that other user in that other thread, and I THINK it might have less bloat than the ATT XT1058 rom.
And I do suggest you read that entire thread... there are a few good posts in there with info that might help you understand the situation... because this is a weird state.

KidJoe said:
Please see -> No OTAs on AT&T XT1058
Please do what is listed in Post #5 and post the results. also include what it says for (bootloader) iswarrantyvoid: and who is the carrier you are using it on?
Click to expand...
Click to collapse
KidJoe said:
Ok, well, seeing those things things, let me reiterate that your phone is in an "unknown" or at least "unusual" state. Anything you do at this point is risky! So its up to you if you really want to do anything (like flashing) or leave it like it is (since its working).
There is a chance you will not get updates if you are using the XT1058 rom branded for another carrier. (i.e. if you have the ATT XT1058 rom on an XT1058 being used on a different carrier).
As for step by step... you have a few options..
http://mark.cdmaforums.com/MotoX-ReturnToStock.html See the requirements at the top of the page, and then option 5
Or...
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Oh, and I only suggested the Rogers Canada XT1058 rom because it worked for that other user in that other thread, and I THINK it might have less bloat than the ATT XT1058 rom.
And I do suggest you read that entire thread... there are a few good posts in there with info that might help you understand the situation... because this is a weird state.
Click to expand...
Click to collapse
Thank you very much for the reply.. I followed your instructions and I am now on 4.4.4. The same happened exactly, home button not working, active display not working, quick settings could not be reached.. FACTORY RESETED it and its working fine now.

[Q] Unusual Boot loader variables in Moto X

I recently bought a used Moto X AT&T Version from a retailer (it's AT&T, back printed with its logo). It's functioning normally. GSM Network is recognized. I was also able to take an OTA upgrade to 4.4.4 (it was previously 4.4.2). Everything is working up to the mark.
Well, I rebooted my phone in Fastboot Mode (just for curiosity) and was completely shocked when I read Device is Unlocked: Status Code 1 printed on the screen. But, I know this variant can't be unlocked and secondly, I have never read about Status Code: 1. My Developer Edition prints Status Code: 3 which is obviously unlocked. Amazed of what I read, I got worried! So I issued fastboot getvar all command to the phone.
The result variables got me more worried! I have added them below for reference:
(bootloader) version-bootloader: 30B7
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Elpida S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x8300
(bootloader) radio: 0x6
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: LXXXXXXXXXX
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: XXF8F3030C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Key pressed
(bootloader) ro.build.date: Wed Jun 25 00:10:28 PDT 2014
(bootloader) ro.build.id: KXA21.12-L1.26
(bootloader) ro.build.tags: bldacfg,release-keys
(bootloader) ro.build.type: user
(bootloader) ro.build.user: dbbuild
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 26
(bootloader) ro.build.version.release: 4.4.4
(bootloader) ro.mot.build.customerid: att
(bootloader) ro.product.name: ghost_att
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.4.4/K
(bootloader) ro.build.fingerprint[1]: XA21.12-L1.26/26:user/bldacfg,re
(bootloader) ro.build.fingerprint[2]: lease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.212.44.26.ghost_att
(bootloader) ro.build.version.full[1]: .ATT.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]: id14) (gcc version 4.7 (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed Jun 25 00:21:2
(bootloader) kernel.version[4]: 1 PDT 2014
Click to expand...
Click to collapse
1. Why the IMEI is being reported as 00000000000..... If I go to System>About>Status, IMEI is being correctly reported. Dialing *#06# also displays the IMEI correctly.
2. Why CID is 0xdead? From my knowledge CID is always a hex value. And what this CID 0xdead implies?
3. Bootloader reports unlocking is not supported. My friend also has a Moto X AT&T. His reports 'no' and also correctly shows IMEI and CID. Why this?
4. Does this means my Moto X is unlocked and I can flash any custom recovery on it? As Device reports it's unlocked.
5. Stock Recovery doesn't seem to work as it always says 'No Command'. Is it safe to flash the stock recovery?
From all this, I have only come to the conclusion that the device was tampered. But how such happened?
Thanks to everyone, who replies!

mfbcool said:
Device is Unlocked: Status Code 1 printed on the screen.
Click to expand...
Click to collapse
That is the factory state.
In bootloader mode do you see AP Fastboot Flash Mode (S) or (NS)?
---------- Post added at 08:23 AM ---------- Previous post was at 08:21 AM ----------
mfbcool said:
From all this, I have only come to the conclusion that the device was tampered. But how such happened?
Thanks to everyone, who replies!
Click to expand...
Click to collapse
Maybe it was a factory device and someone cloned an IMEI onto it - that might be what happened here.
---------- Post added at 08:30 AM ---------- Previous post was at 08:23 AM ----------
mfbcool said:
4. Does this means my Moto X is unlocked and I can flash any custom recovery on it? As Device reports it's unlocked.
Click to expand...
Click to collapse
I think it does. Try flashing TWRP and you will see.
---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------
mfbcool said:
5. Stock Recovery doesn't seem to work as it always says 'No Command'. Is it safe to flash the stock recovery?
Click to expand...
Click to collapse
It is always safe to flash stock, signed files as long as you have the right version for your device.

Thanks JulesJam for the reply!
AP Fastboot Flash Mode is NS (please see picture in the attachment)
I'll try flashing TWRP tonight. Hope everything goes well! If bootloader locked I won't be even able to pass the flashing step, right? (as pre flash signature validation will fail)
Flashed TWRP 2.8.6.0 successfully! Everything is working like a charm.
Flashed Carbon ROM 5.1.1. Working flawlessly!

Where do all those factory devices suddenly come from?

Exactly my question!
dagoban said:
Where do all those factory devices suddenly come from?
Click to expand...
Click to collapse
I think such phones are actually being secretly stolen from the factory or being leeched out secretly. How could it be possible that Motorola sells a bootloader factory unlocked smartphone?

FYI, there are several old threads covering phones in this state.
The oldest example:
http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150

mfbcool said:
Thanks JulesJam for the reply!
AP Fastboot Flash Mode is NS (please see picture in the attachment)
I'll try flashing TWRP tonight. Hope everything goes well! If bootloader locked I won't be even able to pass the flashing step, right? (as pre flash signature validation will fail)
Flashed TWRP 2.8.6.0 successfully! Everything is working like a charm.
Flashed Carbon ROM 5.1.1. Working flawlessly!
Click to expand...
Click to collapse
Flash away dude!!! Just keep in mind that your device is very unsecure in that if you lose it, anyone with any knowledge about these things will be able to do anything they want with that device just like you are able to. They will be able to circumvent any security on the device b/c the fastboot is not secure.
---------- Post added at 07:15 PM ---------- Previous post was at 07:13 PM ----------
mfbcool said:
I think such phones are actually being secretly stolen from the factory or being leeched out secretly. How could it be possible that Motorola sells a bootloader factory unlocked smartphone?
Click to expand...
Click to collapse
They definitely weren't supposed to be sold to retail customers.
These devices didn't have IMEIs and so someone had to put an IMEI on the device, which is shady depending on how the IMEI was obtained.

unknown x, need help idenifiying

just received a lot of defected 2013 x's and one is like i have never seen, it has no branding on bat cover and bootloader is unlocked with 4.2.2 os, it has a very weird home screen with a pic of file folder in right bottom home screen with colored blocks on it, when taped tinnier icons appear, has a test cam, fr on ,settings...., it has no google apps or services with some apps i cant remember ever seeing on a x.
baseband version
msm8960pro_bp_2323.010.71.00r
kernel version
3.4.42-xline-eng-g9c632ef-00003-g99060a2
[email protected] #1
system version
unknown
build number
factory_ghost-userdebug 4.2.2
13.9.0q2.x-118_ghost-gnpo-6 8 test-keys
imei is listed as (0),
in ap fastboot we got, mode (ns)
30.50
was hoping maybe i got some thing that can be useful to one of our respected developers if not what frimware should i try to install?

In the bootloader if you type:
fastboot getvar all
Click to expand...
Click to collapse
You might be able to get a bit more info.

killsforpie said:
In the bootloader if you type:
You might be able to get a bit more info.
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version-bootloader: 3050
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Elpida S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x8300
(bootloader) radio: 0x1
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: TA17607A81
(bootloader) qe:
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: 6D3830040C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Key pressed
(bootloader) ro.build.date: Mon Jul 1 16:34:20 CDT 2013
(bootloader) ro.build.id: 13.9.0Q2.X-118-GHOST_GNPO-6
(bootloader) ro.build.tags: release-keys
(bootloader) ro.build.type: userdebug
(bootloader) ro.build.user: hudsoncm
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 8
(bootloader) ro.build.version.release: 4.2.2
(bootloader) ro.mot.build.customerid:
(bootloader) ro.product.name: factory_ghost
(bootloader) ro.build.fingerprint[0]: motorola/factory_ghost/ghost:4.2
(bootloader) ro.build.fingerprint[1]: .2/13.9.0Q2.X-118-GHOST_GNPO-6/8
(bootloader) ro.build.fingerprint[2]: :userdebug/release-keys
(bootloader) ro.build.version.full:
(bootloader) kernel.version[0]: Linux version 3.4.42-xline-eng-g
(bootloader) kernel.version[1]: 9c632ef-00003-g99060a2 (hudsoncm
(bootloader) kernel.version[2]: @il93lnxdroid50) (gcc version 4.
(bootloader) kernel.version[3]: 6.x-google 20120106 (prerelease)
(bootloader) kernel.version[4]: (GCC) ) #1 SMP PREEMPT Mon Jul
(bootloader) kernel.version[5]: 1 16:57:14 CDT 2013
all:
finished. total time: 0.149s
this device seams to be some test or prototype device, maybe valuable to the right dev, it has no cam app but does have a test cam app also missing a lot of stock apps, app called( rf on) which seams to be some testing app, my pc recognized it as factory_ghost and not model number ,

Where did you get it man.

adity said:
Where did you get it man.
Click to expand...
Click to collapse
it was in a large lot of phones i got at an auction, i have no history, it has to be some sort of test device or prototype? did i mention in first post that bootloader is unlocked? what do you think?

also missing some settings compared to 444
touchless control
motorola connect
motorola privacy
motorola device id
about phone has no (system update)

hugh a said:
just received a lot of defected 2013 x's and one is like i have never seen, it has no branding on bat cover and bootloader is unlocked with 4.2.2 os,
Click to expand...
Click to collapse
In bootloader mode, go to barcodes - it should tell you the model number.
---------- Post added at 08:22 AM ---------- Previous post was at 08:21 AM ----------
hugh a said:
did i mention in first post that bootloader is unlocked? what do you think?
Click to expand...
Click to collapse
Is the unlocked bootloader status code 3 or status code 1?
---------- Post added at 08:43 AM ---------- Previous post was at 08:22 AM ----------
hugh a said:
ro.product.name: factory_ghost
Click to expand...
Click to collapse
My XT1060 retail Verizon model and XT1060 Dev Ed both say:
ro.product.name: ghost_verizon
So what you have likely is a factory model. It should be unlocked status code 1, which is how they are manufactured and then they are locked in the factory and become status code 0.
Can you take a pic of the screen in bootloader mode?

Have you tried a factory reset to see if you get the standard settings + launcher back?

JulesJam said:
In bootloader mode, go to barcodes - it should tell you the model number.
---------- Post added at 08:22 AM ---------- Previous post was at 08:21 AM ----------
Is the unlocked bootloader status code 3 or status code 1?
---------- Post added at 08:43 AM ---------- Previous post was at 08:22 AM ----------
My XT1060 retail Verizon model and XT1060 Dev Ed both say:
ro.product.name: ghost_verizon
So what you have likely is a factory model. It should be unlocked status code 1, which is how they are manufactured and then they are locked in the factory and become status code 0.
Can you take a pic of the screen in bootloader mode?
Click to expand...
Click to collapse
status code 1

dagoban said:
Have you tried a factory reset to see if you get the standard settings + launcher back?
Click to expand...
Click to collapse
yes, no change

hugh a said:
status code 1
Click to expand...
Click to collapse
That's definitely a factory device. Status code 1 unlocked is how they are in the factory before they get locked and shipped out as status code 0 locked.
Also, I believe that AP Fastboot Flash Mode (NS) the NS means not secure unlike on the production models where it is S for secure. I am not sure what this means exactly but I think I read it means you could get fastboot to flash a custom bootloader. Not sure.
Then the bootloader has an additional option - Switch console. Not sure what that means.
I would think a dev would be interested in the device - jcase or beaups in particular since they were the ones to have rooted and unlocked Moto X's in the past.
Obviously the device can never operate as a phone b/c of the lack of an IMEI number - you could clone one but that is illegal.

JulesJam said:
That's definitely a factory device. Status code 1 unlocked is how they are in the factory before they get locked and shipped out as status code 0 locked.
Also, I believe that AP Fastboot Flash Mode (NS) the NS means not secure unlike on the production models where it is S for secure. I am not sure what this means exactly but I think I read it means you could get fastboot to flash a custom bootloader. Not sure.
Then the bootloader has an additional option - Switch console. Not sure what that means.
I would think a dev would be interested in the device - jcase or beaups in particular since they were the ones to have rooted and unlocked Moto X's in the past.
Obviously the device can never operate as a phone b/c of the lack of an IMEI number - you could clone one but that is illegal.
Click to expand...
Click to collapse
im very interested in donating the board to the right dev could you please put the word out, this was the main purpose of me starting this thread, you are right the more i thought about it what good would it be to install os with out imei and i for sure dont even want to go there!
so jcase or beaups if you are interested pm me.

hugh a said:
im very interested in donating the board to the right dev could you please put the word out, this was the main purpose of me starting this thread, you are right the more i thought about it what good would it be to install os with out imei and i for sure dont even want to go there!
so jcase or beaups if you are interested pm me.
Click to expand...
Click to collapse
You have to put an @ in front of their names like this to get them notified
@jcase @beaups - @hugh a has a factory moto x 2013 that he would like to donate to a dev if you would like it as a test device. It is status code 1 unlocked with fastboot flash mode (NS) as shown in the pics this thread. Please PM him if you are interested.
The bootloader is version 30.50, which I have never seen before. I think the earliest bootloader released for sale was the 30.70. And this factory device has an additional option in the bootloader menu - Switch Console. It doesn't have an IMEI. He bought it in an auction of a batch of moto x's.

JulesJam said:
You have to put an @ in front of their names like this to get them notified
@jcase @beaups - @hugh a has a factory moto x 2013 that he would like to donate to a dev if you would like it as a test device. It is status code 1 unlocked with fastboot flash mode (NS) as shown in the pics this thread. Please PM him if you are interested.
The bootloader is version 30.50, which I have never seen before. I think the earliest bootloader released for sale was the 30.70. And this factory device has an additional option in the bootloader menu - Switch Console. It doesn't have an IMEI. He bought it in an auction of a batch of moto x's.
Click to expand...
Click to collapse
JulesJam :good:

Safe to go back to 5.1 after flashing the 6.0 Brazil update?

Is it safe and as simple as flashing that list of fastboot commands I.e. fastboot flash sparsechunk 1, 2, etc. I'd rather go back to 5.1 and take the ota once it comes. Safe to do? Thanks

supremekizzle said:
Is it safe and as simple as flashing that list of fastboot commands I.e. fastboot flash sparsechunk 1, 2, etc. I'd rather go back to 5.1 and take b e the ota once it comes. Safe to do? Thanks
Click to expand...
Click to collapse
Me too, the same situation.
just only problem is, that a lost the baseband.
it may be easier to downgrade too.
i'm follow this post.

Viniciusnpor said:
Me too, the same situation.
just only problem is, that a lost the baseband.
it may be easier to downgrade too.
i'm follow this post.
Click to expand...
Click to collapse
Yes you can downgrade to 5.1. But absolutely do NOT take an OTA to 6.0 because it will almost certainly cause a brick.
Sent from my XT1095 using Tapatalk

AGISCI said:
Yes you can downgrade to 5.1. But absolutely do NOT take an OTA to 6.0 because it will almost certainly cause a brick.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
The bootloader in 6.0 marshmallow on XT 1092 is exactly the same as 5.1 (60.16). In theory, I think it would be possible to downgrade to 5.1 via image flash and then OTA update to 6.0.
As a matter of fact, I flashed Brazilian Marshmallow on my XT 1092 (except the bootloader and partition table) and then downgraded to 5.1 image today, and took the OTA to 6.0 from Motorola. Phone works fine, and I see the bootloader is same as before.

This is the "getvar all" from my Canadian XT1097 with RETBR 6.0 and RETCA 5.1 modem/radio:
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) cid: 0x000E
(bootloader) channelid: 0x80
(bootloader) uid: D5E3D30F0B000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 03-12-2015
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Dec 15 16:36:47 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retbr/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPE24.49-18/15:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.11.18.victara_ret
(bootloader) ro.build.version.full[1]: br.retbr.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_4235210.110.09.16R VICTARA_R
(bootloader) version-baseband[1]: ETCA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-ga9982b3-00002-g389
(bootloader) kernel.version[1]: e46b ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .8 (GCC) ) #1 SMP PREEMPT Tue Nov 3 16:1
(bootloader) kernel.version[3]: 2:18 CST 2015
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: retca
(It's running just fine, no problems)

AGISCI said:
Yes you can downgrade to 5.1. But absolutely do NOT take an OTA to 6.0 because it will almost certainly cause a brick.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Why would that be?

supremekizzle said:
Why would that be?
Click to expand...
Click to collapse
Because: http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147

supremekizzle said:
Why would that be?
Click to expand...
Click to collapse
if you do that you may run a chance of hard bricking your phone....

tyus2 said:
Because: http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147
Click to expand...
Click to collapse
So when someone captures the xt1095 6.0 update can I just flash that? That way it's a normal US xt1095?

supremekizzle said:
So when someone captures the xt1095 6.0 update can I just flash that? That way it's a normal US xt1095?
Click to expand...
Click to collapse
No, you would have to wait for the full firmware, not the OTA.
Sent from my XT1095 using Tapatalk

AGISCI said:
No, you would have to wait for the full firmware, not the OTA.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Damn. I should've never flashed that. Would the full firmware be the one on the Moto firmware page, when it becomes available? Or does XDA usually get their hands on it before them? Sorry if you don't know these answers, you just know more than me so I took a shot...

supremekizzle said:
Damn. I should've never flashed that. Would the full firmware be the one on the Moto firmware page, when it becomes available? Or does XDA usually get their hands on it before them? Sorry if you don't know these answers, you just know more than me so I took a shot...
Click to expand...
Click to collapse
Usually it appears in 3 places. The motorola website, filefactory, and motorolafirmware.center. If you get it from either of these 3 places you should be fine.
Sent from my XT1095 using Tapatalk

Would I be in the same boat since I put the BR 6.0 update onto my XT1095 via a TWRP backup?

some_shyguy said:
Would I be in the same boat since I put the BR 6.0 update onto my XT1095 via a TWRP backup?
Click to expand...
Click to collapse
No. The twrp backup does not flash the partition table nor the bootloader, so you are fine.
Sent from my XT1095 using Tapatalk

What if the 6.0 update has same bootloader and partition table as the 5.1 firmware? It would be safe to restore to 5.1 and take the 6.0 OTA then? I see that the bootloader is same in Marshmallow as Lollipop 5.1 (BL ver-60.16).

tyus2 said:
What if the 6.0 update has same bootloader and partition table as the 5.1 firmware? It would be safe to restore to 5.1 and take the 6.0 OTA then? I see that the bootloader is same in Marshmallow as Lollipop 5.1 (BL ver-60.16).
Click to expand...
Click to collapse
I flashed the full RETCA 5.1 firmware over the RETBR 6.0 and it's working fine (even flashed the bootloader and partition table). But I have no idea when, and if, I will get the 6.0 update for Canada, as we are always the last country on earth to get the updates (if at all).

tyus2 said:
What if the 6.0 update has same bootloader and partition table as the 5.1 firmware? It would be safe to restore to 5.1 and take the 6.0 OTA then? I see that the bootloader is same in Marshmallow as Lollipop 5.1 (BL ver-60.16).
Click to expand...
Click to collapse
Theoretically yes, but there is one problem in your assumption. Remember that there are different models, xt1092, xt1093, xt1094, xt1095, xt1095, etc. Sometimes the different models might be different bootloader and partition tables. So for example I change from xt1092 to xt1097 brazil for 6.0. But if the brazil bootloader and partition table were different there it could cause a brick. It is better to warn people about the dangers of downgrades because it is a large cause of bricks. For example i had this happen to a friend. He had a moto g on 4.4.4 from chile. He then flashed the 4.4.4 from europe to take an ota to 5.0. It worked. But the bootloader and partition from the 5.0 from europe and the one from south america were not the same. So he went back to 4.4.4 from south america then took the ota to 5.0 and it bricked. The moral of the story is that the bootloader and partition table for 5.0 in one model is not necessarily the same in another model. If you are 100% sure that the partition did not change when you upgraded then sure taking an OTA is safe. But remember that many of these people are changing their phone to the brazil 6.0... so when they downgrade and revert to their correct firmware there is a high probability of brick from an OTA from the difference in bootloaders and partitions. It is better to warn them so that they don't end up with a phone that is bricked and no way to unbrick it.
Sent from my XT1095 using Tapatalk

AGISCI said:
Theoretically yes, but there is one problem in your assumption. Remember that there are different models, xt1092, xt1093, xt1094, xt1095, xt1095, etc. Sometimes the different models might be different bootloader and partition tables. So for example I change from xt1092 to xt1097 brazil for 6.0. But if the brazil bootloader and partition table were different there it could cause a brick. It is better to warn people about the dangers of downgrades because it is a large cause of bricks. For example i had this happen to a friend. He had a moto g on 4.4.4 from chile. He then flashed the 4.4.4 from europe to take an ota to 5.0. It worked. But the bootloader and partition from the 5.0 from europe and the one from south america were not the same. So he went back to 4.4.4 from south america then took the ota to 5.0 and it bricked. The moral of the story is that the bootloader and partition table for 5.0 in one model is not necessarily the same in another model. If you are 100% sure that the partition did not change when you upgraded then sure taking an OTA is safe. But remember that many of these people are changing their phone to the brazil 6.0... so when they downgrade and revert to their correct firmware there is a high probability of brick from an OTA from the difference in bootloaders and partitions. It is better to warn them so that they don't end up with a phone that is bricked and no way to unbrick it.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
So as of right now since I flashed Brazil 5.1 and then flashed Brazil 6.0, there is no safe way to get back to US 5.1 to take the 6.0 ota. The best course of action is to flash XT1095 6.0 when it's available, which should be the next week or so?
But it won't be just flashing the ota, it'll be flashing everything in the firmware to get back to US version?

supremekizzle said:
So as of right now since I flashed Brazil 5.1 and then flashed Brazil 6.0, there is no safe way to get back to US 5.1 to take the 6.0 ota. The best course of action is to flash XT1095 6.0 when it's available, which should be the next week or so?
But it won't be just flashing the ota, it'll be flashing everything in the firmware to get back to US version?
Click to expand...
Click to collapse
Yes, you will have to flash everything.
Sent from my XT1095 using Tapatalk

From RETCA 5.1 to RETBR 6.0, back to RETCA 5.1, and just now received the RETCA 6.0 OTA, updated without any problems.
Screenshot:
http://forum.xda-developers.com/showpost.php?p=64366441&postcount=232