AT&T XT1058 - Stuck on 4.2.2

[OmMeE]

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.

 

[OmMeE]

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)

 

[KidJoe]

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?

 

[OmMeE]

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

 

[OmMeE]

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.

 

[KidJoe]

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.

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.

 

[OmMeE]

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.

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.

 

[KidJoe]

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.

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.

 

[OmMeE]

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?

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.

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.