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.

[Q&A] [Firmware] 7.15.401.1 HTC One M7 Latest • No Red Warning • No Wipe

Q&A for [Firmware] 7.15.401.1 HTC One M7 Latest • No Red Warning • No Wipe
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Firmware] 7.15.401.1 HTC One M7 Latest • No Red Warning • No Wipe. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Hi, getting following error message
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 3.305s
what can i do

unplayed_namer said:
Hi, getting following error message
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 3.305s
what can i do
Click to expand...
Click to collapse
Are you flashing it in recovery or RUU mode?

matanlevanon said:
Are you flashing it in recovery or RUU mode?
Click to expand...
Click to collapse
over adb in RUU mode
is it possible it to flash over TWRP ?

unplayed_namer said:
over adb in RUU mode
is it possible it to flash over TWRP ?
Click to expand...
Click to collapse
NOt possible through TWRP.
you have to use fastboot mode and flash it in oem rebootRUU mode.
Follow This guide and read through "Section 2: Firmware Upgrade" and follow every step.
You should get FAIL for the first time and re-flash it right away...

Installed 7.15.401.1 today on stock Lollipop 5.0.1. No issues so far but will report back if I run into any. Many thanks!

can i flash this while using 4.4.3? thinking of upgrading to lolipop later
Sent from my HTC One using XDA Premium 4 mobile app

Ikmalblack95 said:
can i flash this while using 4.4.3? thinking of upgrading to lolipop later
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes

I'm currently on a stock HTC one M7 with S-off and 4.4.3 with software 6.09.401.11
Can I safely Flash this without wiping my phone or getting trouble with running my phone?
I'm waiting for the official lollipop update from HTC to pop up on my phone and just wondering what this firmware can already do for me

Hi,
I'm S-OFF, and have ViperROM 4.4.3 installed.
I've never upgrade my firmware, so currently on 1.29.401.16. Would there be any issues flashing this?
Thanks for your help.

Rubman said:
I'm currently on a stock HTC one M7 with S-off and 4.4.3 with software 6.09.401.11
Can I safely Flash this without wiping my phone or getting trouble with running my phone?
I'm waiting for the official lollipop update from HTC to pop up on my phone and just wondering what this firmware can already do for me
Click to expand...
Click to collapse
If you are waiting for official Lollipop from HTC there is no point of flashing this, though you can.
The official update will have a FW update that will override this one...

matanlevanon said:
If you are waiting for official Lollipop from HTC there is no point of flashing this, though you can.
The official update will have a FW update that will override this one...
Click to expand...
Click to collapse
Then what will this FW update do for me if I install it?
Or is it at the moment more of a look at me showing off with the newest firmware?

Rubman said:
Then what will this FW update do for me if I install it?
Or is it at the moment more of a look at me showing off with the newest firmware?
Click to expand...
Click to collapse
It is the newest FW, what exactly was changed, I have no idea...

What should i do ?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA36FWxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
My device is s-off and supercid. I want to update my firmware to lastest version but my firmware version is too old "2.24.401.2" and i am using ARHD 83.1 rom and Elemental-X 18.0 kernel. Can i upgrade directly to lastest firmware ?

mrdtr said:
My device is s-off and supercid. I want to update my firmware to lastest version but my firmware version is too old "2.24.401.2" and i am using ARHD 83.1 rom and Elemental-X 18.0 kernel. Can i upgrade directly to lastest firmware ?
Click to expand...
Click to collapse
It is recommended that you flash all of the FW versions one after the other...
you can find all of them on Vomer's page

matanlevanon said:
It is recommended that you flash all of the FW versions one after the other...
you can find all of them on Vomer's page
Click to expand...
Click to collapse
Thank you, i successfully updated my firmware to 7.15.401.1

m_w_clarke said:
Hi,
I'm S-OFF, and have ViperROM 4.4.3 installed.
I've never upgrade my firmware, so currently on 1.29.401.16. Would there be any issues flashing this?
Thanks for your help.
Click to expand...
Click to collapse
After reading around the subject, I did incremental updates to the firmware from 1.29.X all the way to 7.15 following Vomer's guide and have been successful.
Still on Jellybean. Still S-OFF.
Hope others find this useful

cant flash the 7.15.401.1
hello there, thank you for all the info. my m7 is s-off, hboot 1.55, i could flash this firmware 6.09.401.12 but it doesn't work for the 7.15.401.1... any idea why? thank you!

my computer is not recognizing the phone when its in fastboot mode and with everytime i right a fastboot command i'll get < waiting for devices > msg on the cmd
im almost frustrated from this because i have downloaded the latest drivers as well as tried Samsung ones
from exploring the web i found that it might be a windows 8 problem with the usb 3.0 ports.
can someone help?

Baderf17 said:
my computer is not recognizing the phone when its in fastboot mode and with everytime i right a fastboot command i'll get < waiting for devices > msg on the cmd
im almost frustrated from this because i have downloaded the latest drivers as well as tried Samsung ones
from exploring the web i found that it might be a windows 8 problem with the usb 3.0 ports.
can someone help?
Click to expand...
Click to collapse
It is, try USB 2 and there should be a thread with the correct drivers
Sent from HTC One

Touchscreen not working!

I recently flashed the TeamUB rom and forgot to do a factory data reset, now my touchscreen wont work. How can I fix this?
Thank you
Xanoas

You could try a clean reflash.

Tel864 said:
You could try a clean reflash.
Click to expand...
Click to collapse
How can I do that? My touchscreen wont work even in recovery, im using twrp.

Flash via Minmal ADB & Fastboot and use adb commands. Hope your USB-debugging is enabled.

Xanoas said:
How can I do that? My touchscreen wont work even in recovery, im using twrp.
Click to expand...
Click to collapse
Wolfcity said:
Flash via Minmal ADB & Fastboot and use adb commands. Hope your USB-debugging is enabled.
Click to expand...
Click to collapse
You could flash a new kernel. Boot to fastboot and flash a kernel.. any kernel. It will most likely fix your issue. If not flash a kernel for cm11 and then flash cm11 in twrp

Why recently this issue is coming with every other user that by flashing certain roms their touchscreens stopped working?
Sent from my Moto G 2014

pranshubatra707 said:
Why recently this issue is coming with every other user that by flashing certain roms their touchscreens stopped working?
Sent from my Moto G 2014
Click to expand...
Click to collapse
CurbThePain said:
You could flash a new kernel. Boot to fastboot and flash a kernel.. any kernel. It will most likely fix your issue. If not flash a kernel for cm11 and then flash cm11 in twrp
Click to expand...
Click to collapse
Wolfcity said:
Flash via Minmal ADB & Fastboot and use adb commands. Hope your USB-debugging is enabled.
Click to expand...
Click to collapse
pp
My friend who also had the same phone had the same problem he ended up returning it to argos even after a month so that's what I'm going to do hopefully they accept it back, if it does not then I'll try these methods. Thx guys!

has anyone found a solution for this issue? i cant return it since im not in the US anymore and motorolla doesnt support the device in my current country (Venezuela). its driving me crazy because the cellphone works (recieves calls and messages, conencts to wifi, takes screenshots) but the touchscreen doesnt let me do anything :crying:

tostado3 said:
has anyone found a solution for this issue? i cant return it since im not in the US anymore and motorolla doesnt support the device in my current country (Venezuela). its driving me crazy because the cellphone works (recieves calls and messages, conencts to wifi, takes screenshots) but the touchscreen doesnt let me do anything :crying:
Click to expand...
Click to collapse
Just boot into bootloader(you dont need working touchscreen for that) and follow this
http://forum.xda-developers.com/showthread.php?p=55373304
Sent from my XT1068

pranshubatra707 said:
Just boot into bootloader(you dont need working touchscreen for that) and follow this
http://forum.xda-developers.com/showthread.php?p=55373304
Sent from my XT1068
Click to expand...
Click to collapse
i restored my device to stock, still have the same issue. display works cellphone does too, its just the touchscreen wich seems to be dead no response at all :crying:
Thanks for the help, if you think of another solution let me know!

tostado3 said:
i restored my device to stock, still have the same issue. display works cellphone does too, its just the touchscreen wich seems to be dead no response at all :crying:
Thanks for the help, if you think of another solution let me know!
Click to expand...
Click to collapse
It might be a hardware problem then?
Sent from my XT1068

pranshubatra707 said:
It might be a hardware problem then?
Sent from my XT1068
Click to expand...
Click to collapse
i belive so, i already disassembled the phone myself, i would like to test the screen in another friends phone before buying a replacement for it, to make sure its just the screen.
thank you very much for your help and time i really appreciate it! :good:

tostado3 said:
i belive so, i already disassembled the phone myself, i would like to test the screen in another friends phone before buying a replacement for it, to make sure its just the screen.
thank you very much for your help and time i really appreciate it! :good:
Click to expand...
Click to collapse
Ha, I don't have a good enough friend that will let me disassembled their phone for testing purposes.

tostado3 said:
i belive so, i already disassembled the phone myself, i would like to test the screen in another friends phone before buying a replacement for it, to make sure its just the screen.
thank you very much for your help and time i really appreciate it! :good:
Click to expand...
Click to collapse
No problem..do let us know the real cause when you find it
Sent from my XT1068

workaround
We came along this thread while having the same issue. I got it fixed even though I was half convinced that it is a hardware issue as it occurs in the recovery and the independent system.
My history to the touch error is:
cm12->backup-> wipe+install Titan Z->wipe+install microkat-> restore cm12.
The only way to access the device was fastboot for me.
A strange thing I noted was the output of getvar, which didn't change no matter what I did (fastboot flash boot boot.img, fastboot flash motoboot motoboot.img, recovery or booting antoher kernel via fastboot).
#fastboot getvar all
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:4.4.4/KXB21.85-14/9:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.14.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(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:
(bootloader) kernel.version[0]: Linux version 3.4.42-pINKman-kk4.4 (sluk
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.7 (GCC) ) #15021
(bootloader) kernel.version[2]: 9 SMP PREEMPT Thu Feb 19 15:31:25 CET 20
(bootloader) kernel.version[3]: 15
That Pinkman kernel came actually from Microkat, but I have no idea why this is in the bootloader and I suppose it as kernel or a signature didn't work with the drivers.
A friend suggested to flash the system partition as well with the stock rom. Before we actually installed other roms via sideload but the issue didn't change.
Now follow this thread to flash stock on the device:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
This is made for Windows, but you can download the file and see a batch script (Auto restore) which is like some other sources in the internet; instead of mfastboot you can use fastboot. The other stuff can stay the same.
My touch is working again and the fastboot getvar output is different now:
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.99-16/10:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(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: MSM8626BP_1032.3112.96.00R EMEA_DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-ge35b7bb-00001-gf6a
(bootloader) kernel.version[1]: 3942 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .8 (GCC) ) #1 SMP PREEMPT Wed Feb 25 01:
(bootloader) kernel.version[3]: 09:46 CST 2015
And the baseband value is populated again.
Don't throw away the phone yet
Hope this helps.

XT1069
My problem it's the same ( with flashing MicroKat and trying to get back to CM12 ) , but my phone model is XT1069 , theres some way can i do to fix this? ( Sorry for the bad english ). :crying:

Amazon Fire Bootloader unlock code??

So when i entered the fastboot getvar all command in adb
Heres what i got
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) max-download-size: 134217728
(bootloader) partition-size:userdata: 17329be00
(bootloader) partition-type:userdata: unknown
(bootloader) partition-size:cache: fa00000
(bootloader) partition-type:cache: unknown
(bootloader) partition-size:system: 4b000000
(bootloader) partition-type:system: unknown
(bootloader) partition-size:TEE2: 500000
(bootloader) partition-type:TEE2: unknown
(bootloader) partition-size:TEE1: 500000
(bootloader) partition-type:TEE1: unknown
(bootloader) partition-size:LOGO: 380000
(bootloader) partition-type:LOGO: unknown
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: unknown
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-size:EXPDB: 1160000
(bootloader) partition-type:EXPDB: unknown
(bootloader) partition-sizeKB: 100000
(bootloader) partition-typeKB: unknown
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) off-mode-charge: 1
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: FORD
(bootloader) version: 0.5
(bootloader) unlock_status: false
(bootloader) unlock_version: 1
(bootloader) unlock_code: 0xaXXXXXXXXXXX
(bootloader) prod: 1
all: Done!!
finished. total time: 0.180s
Im wondering if the unlock code can be used to unlock it or its just the binary data on true or false.

@sd_shadow Your thoughts on this?

This maybe useful or maybe not.
Link for the kindle hdx 8.9
[DEV] Bootloader unlock procedure and software by @dpeddi

Ugh wish i had another kindle fire

sd_shadow said:
This maybe useful or maybe not.
Link for the kindle hdx 8.9
[DEV] Bootloader unlock procedure and software by @dpeddi
Click to expand...
Click to collapse
Apparently I just tried this with the one Getvar gave me it didnt work. gave me an unlock code error

I bought this fire for my son. The hdx unlock worked until 3.2.4 firmware and is based on a bug on image verification. Probably we can't unlock any more the bootloader..both on newer HDx and on this cheap fire.

@sd_shadow So what's the status on the bootloader unlock? Anything us common users can do to help?
Would making a petition online to Amazon help our cause? Or maybe get @geohot involved if possible?

rjmxtech said:
@sd_shadow So what's the status on the bootloader unlock? Anything us common users can do to help?
Would making a petition online to Amazon help our cause? Or maybe get @geohot involved if possible?
Click to expand...
Click to collapse
Dude can you layoff for a bit? You're saying the same things in every thread. The bootloader isn't unlocked, most likely won't be. Amazon won't break for a petition, and geohot works for google. Be patient, the constant hounding doesn't make it work faster...

ldeveraux said:
Dude can you layoff for a bit? You're saying the same things in every thread. The bootloader isn't unlocked, most likely won't be. Amazon won't break for a petition, and geohot works for google. Be patient, the constant hounding doesn't make it work faster...
Click to expand...
Click to collapse
Um, this is one of the only threads I have posted this in. Calm yourself. I am just trying to see what I can do. Trying to do things is better than sitting and doing nothing and waiting for others to do them for you.

rjmxtech said:
Um, this is one of the only threads I have posted this in. Calm yourself. I am just trying to see what I can do. Trying to do things is better than sitting and doing nothing and waiting for others to do them for you.
Click to expand...
Click to collapse
look, I get it, you really want the bl unlocked. You posted in 3 threads about it, one had to be cleaned. But unless you know anything about the process, there's nothing to help with. I'm not discouraging, it's just the way it is. Let those in the know alone, leave them to their work. Trust me, you won't miss anything if it happens

ldeveraux said:
look, I get it, you really want the bl unlocked. You posted in 3 threads about it, one had to be cleaned. But unless you know anything about the process, there's nothing to help with. I'm not discouraging, it's just the way it is. Let those in the know alone, leave them to their work. Trust me, you won't miss anything if it happens
Click to expand...
Click to collapse
That one I posted in the wrong place I changed to "nvm" when I realized I posted in the wrong place but I get what you're saying.

well i bricked my fire today trying to install cm12:crying: seems the recovery img was corrupted some how so ill need the bl to be unlocked to flash a custom one. i have reached the limits of my knowledge, as limited as it may be. rooting for those of you that know what you are doing. thank you for the effort, even if it doesnt result in a fix.

jwalb89 said:
well i bricked my fire today trying to install cm12:crying: seems the recovery img was corrupted some how so ill need the bl to be unlocked to flash a custom one. i have reached the limits of my knowledge, as limited as it may be. rooting for those of you that know what you are doing. thank you for the effort, even if it doesnt result in a fix.
Click to expand...
Click to collapse
What are the symptoms of your brick? Can you get to fastboot?

Drax TD said:
What are the symptoms of your brick? Can you get to fastboot?
Click to expand...
Click to collapse
I do have access to fastboot, but not to recovery as stated so no adb commands for me... on normal boot it goes to the cm12 boot logo, and continues attempting to boot.

Shouldn't he be able to recover if he gets boot image and fastboot?
Sent from my KFFOWI using Tapatalk

Franzferdinan51 said:
Shouldn't he be able to recover if he gets boot image and fastboot?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
fastboot mode doesn't work with 5.1.1 bootloader
Sent from my XT1060 using Tapatalk

sd_shadow said:
fastboot mode doesn't work with 5.1.1 bootloader
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Are you sure because I'm pretty sure I used fastboot to restore my tablet when it bricked though I could be wrong may have been adb side load
Sent from my KFFOWI using Tapatalk

Franzferdinan51 said:
Are you sure because I'm pretty sure I used fastboot to restore my tablet when it bricked though I could be wrong may have been adb side load
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.

jwalb89 said:
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.
Click to expand...
Click to collapse
Ahh well good luck can't wait too see what you come up with would love to have a real recovery instead of flash fire
Sent from my KFFOWI using Tapatalk

jwalb89 said:
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.
Click to expand...
Click to collapse
Any luck getting a update.zip that can restore stock using fastboot?
Thanks

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