[HELP THREAD] Moto X Ask any question

Do you think this is an useful post?


  • Total voters
    68

KidJoe

Inactive Recognized Contributor
Aug 23, 2008
3,208
1,560
0
Thorndale/Romansville, PA

bk Thomte

Member
Jan 8, 2016
6
0
0
flashing cm12.1

I m new to this forum so please understand if i am asking a qurstion that has been already asked. There were more than 250 pages so could not go through all the pages .

I would like to flash cm12.1 on my xt1052 asia retail. I have checked the posts of various people. Some saying you do not need to flash cm 11 from stock rom but some say the other way. Either way will it work if i just dirty flash it. I am using twrp v 2.8.7 and supersu v2.46. And if anyone can let me know if i need to flash cm11 first.
Thanks in advance
 

nehuy

Senior Member
Feb 12, 2012
100
15
0
Bariloche
A few days late, but if you still need help:
Try to flash 12.1, it will mostly boot without problem, If you get a bootloop you can try a hard reset, and If that doesn't work, installing cm11 and then 12.1 should solve the problem.
It is a matter of phone version if I'm not mistaken (but can't be certainly sure).
 
  • Like
Reactions: bk Thomte

br0adband

Senior Member
Mar 28, 2008
1,718
779
0
Just grabbed a Sprint Moto X (XT1056) and because I have experience with the AT&T and T-Mobile variants, here's my situation: I'd like to carrier unlock it and Sprint's own website shows I can (potentially) get the DSU (Domestic SIM Unlock) code from them by asking the previous owner to call in and ask for it - the previous owner said they'd do that if I wanted so I'll most likely be asking them for it instead of using samwathegreat's unlock method.

The instructions for entering the code are fairly straightforward as most anyone knows:

Turn off the phone, insert a non-Sprint nanoSIM in the device, when it powers back on it'll stop and ask for the network unlock code which needs to be entered properly because if you do it wrong a number of times (I think most devices limit it to 10 attempts then the device becomes permanently locked forever regardless).

So, my situation at the moment is that I just unlocked the bootloader (since the Sprint variant can be - it's 2+ years old now so no worries about the damned warranty obviously), flashed the clean 4.4.4 final build on it and... well, when I put a T-Mobile SIM in it I'm never prompted for a network unlock code as I should be.

I've confirmed to the best of my ability that the phone isn't already unlocked (not really sure how to do that except try various nanoSIM cards and none of them trigger the network unlock code entry screen and of course none of them work. The only Sprint nanoSIM I have around has no service at all so it's effectively useless.

If I do end up getting the DSU (not the ISU for International use), how the hell am I supposed to enter it? :)

Does anyone know if there's a dialer code that will trigger the network unlock code entry screen to appear? I have the MSL (I think since it's 6 digits and I know a network unlock code should be longer but who knows).

Right now I'm just gonna sit and wait till I hear something from someone, either the friend or whoever might be able to assist here. Doing a bunch of searches for "network unlock code entry" has proven fruitless so far.

Any help or suggestions are appreciated, and for the record yes I did a ##72786# reset earlier as well.
 
Last edited:

skiddyfisk

New member
Jan 24, 2016
3
1
0
Hi there. I've got a Verizon XT1060 on stock 5.1 I'm using on t-mobile. Moving the sim over from my Note and putting in the correct APN info got me up and running flawlessly EXCEPT my hotspot doesn't work.

I've got hotspot service, of course, and it worked without issue on my Note. What happens is the hotspot turns on, the wireless AP goes up, and I can connect to it. At that point, the device I connect with can't access the internet, even though the phone can. The error message is the standard "your device is not connected to the internet", not a "you've used up your data" page or whatever - t-mobile's site says I'm nowhere near the cap, anyway.

I've been all over t-mobile and motorola for support and they all insist it's the other guy's problem. Is there some hidden configuration I can do on this thing to get this working? Failing that is there any non-root app that will give me a usable hotspot?
 

sd_shadow

Recognized Contributor
Sep 21, 2011
16,633
7,544
253
South Dakota
goo.gl
Hi there. I've got a Verizon XT1060 on stock 5.1 I'm using on t-mobile. Moving the sim over from my Note and putting in the correct APN info got me up and running flawlessly EXCEPT my hotspot doesn't work.

I've got hotspot service, of course, and it worked without issue on my Note. What happens is the hotspot turns on, the wireless AP goes up, and I can connect to it. At that point, the device I connect with can't access the internet, even though the phone can. The error message is the standard "your device is not connected to the internet", not a "you've used up your data" page or whatever - t-mobile's site says I'm nowhere near the cap, anyway.

I've been all over t-mobile and motorola for support and they all insist it's the other guy's problem. Is there some hidden configuration I can do on this thing to get this working? Failing that is there any non-root app that will give me a usable hotspot?
guessing that you need to remove the Verizon hotspot checks, that prevents those who still have unlimited data with Verizon, from hotspotting

Sent from my Amzn KFFOWI using XDA Labs
 

skiddyfisk

New member
Jan 24, 2016
3
1
0
I found a non-rooting solution!

I just had to set the APN type to "DUN". It works great now. I would link to the thread where I found it but the forums won't let me. But it was a thread on the motorola forums about a similar issue on the Moto G.
 
  • Like
Reactions: sd_shadow

clotveins

Senior Member
Feb 2, 2012
91
8
0
33
republics of banana island
Need your help here guys. My XT1052 switched off due to low battery while upgrading to lolipop via ota. (I know i messed up a big time.. But it wasnt me who did upgrading)

Now, the phone is working fine except battwry life and lost of touch at times.*

1. Have to charge my phone a couple of times in a single day, and it takes around 5 to 10 minutes to restart (keeps on optimizing apps every single time post boot)

2. There are frequest lost touches. Need to click a couple of times at random locations to get my touch registered.

P.s. i have resetted my phone around 3-4 times since then. It is on stock and unrooted.

Any suggestions on what could possibly be done?
 

sd_shadow

Recognized Contributor
Sep 21, 2011
16,633
7,544
253
South Dakota
goo.gl
Need your help here guys. My XT1052 switched off due to low battery while upgrading to lolipop via ota. (I know i messed up a big time.. But it wasnt me who did upgrading)

Now, the phone is working fine except battwry life and lost of touch at times.*

1. Have to charge my phone a couple of times in a single day, and it takes around 5 to 10 minutes to restart (keeps on optimizing apps every single time post boot)

2. There are frequest lost touches. Need to click a couple of times at random locations to get my touch registered.

P.s. i have resetted my phone around 3-4 times since then. It is on stock and unrooted.

Any suggestions on what could possibly be done?
flash firmware with RSD Lite

Sent from my Motorola XT1060 using XDA Labs
 
  • Like
Reactions: clotveins

mistaboerns

Member
Jan 23, 2016
8
1
0
Schwechat
Hi guys,

I resently installed CM12.1-20151117 on my Moto X XT1052.
The reason I installed CM is that I got the "couldn't connect to camera" bug a lot. Unfortunately the bug is still there. I tried the restart camera apk with the cm camera fix app, renaming the DCIM folder, clearing the app data (camera and gallery) and multiple reboots as well as any combination of these fixes.
Sometimes one of the above solutions will work, but most of the time I end up with only the front camera working.

Does anyone have a working solution for this very annoying bug?
Thank you in advance!

Gesendet von meinem SHIELD Tablet mit Tapatalk
Hi

I had a very similar issue for months now. Had rooted stock 5.1 before, now running CM12.1 release version by SNAPSHOT for a week or so on my XT1052 ghost. Initially that didn't help and I was just about to start living with that, my camera app exclusively started my front cam, not even any error about the camera being busy or something came up, it was simply not there (as Apps like Droid Info didn't find it eihter). I tried many different camera apps, no improvement. Just today it works again (let's see how long it lasts). Can't really figure out why, the only thing I changed yesterday was erasing the modemst1 and modemst2 via fastboot to get my GPS fixed (which worked btw). So if you want (and we seem to have the same model and software) you can try that, but no guarantee ;) (Actually I don't see how that should be connected, but whatever) Good luck!

---------- Post added at 21:54 ---------- Previous post was at 21:26 ----------

Hello everybody,

as I now read all 48 pages of this thread, I feel free to ask a few questions that bother me. Please be patient.

I'm using CM12.1 by SNAPSHOT release ( https://download.cyanogenmod.org/?de...&type=snapshot ) for 7 days now. No problems of any kind with the ROM itself, exceptfor a GPS bug, which I could fixwith erasing the modemst1 and 2. My XT1052 was rooted before already by it's previous owner, bootloader unlocked.

----CM 12.1-20151117-SNAPSHOT-YOG7DAO1K9-ghost
Baseband MSM8960PRO_BP_23255.138.89.00R
Kernel 3.4.42-gd544eb6 [email protected]#1
build date Tue Nov 17 01:42:25 PST 2015
build number cm_ghost-userdebug 5.1.1 LMY48Y c9cc14bc94 test-keys----

Some tweaks done: Xposed with modules, especially Gravity Box, Greenify...

BUT now some questions came up, since I read a lot about Ambient display/Active display/Moto display and got confused about the differences in wording. So, imho "Active display" was the 4.4 feature, which was simply perfect (unfortunately I smashed the display and bought a used, rooted MOTO X with Android 5.1), "Moto display" the 5.1 feature and still good, and now "Ambient display" wants to be the successor (for any model). Am I right here? However, it's hard to believe that. I activated it in the CM12 settings (like everything, under "Gestures" I activated "Ambient display", "Pick-up", "Hand wave"). So far I can't really say the result satisfies me in any way. After reception of a notification Ambient display activates a couple of times, so far so good. Hand waving doesn't work, activating it by picking it up doesn't work. I have no possibility to activate it intentionally. So what's that for then? Is that a bug or normal behaviour? A websearch gave me contradictory results, maybe someone can clarify that for me.

Thanks
 
Last edited:

Sashwat Deb

New member
Feb 18, 2015
4
1
0
Does returning to stock using RSD lite or manual flashing also return the partition filesystems to default. I may have messed with the /data partition file system, will flashing to stock change it to default?
 

Sp!n

Member
Dec 11, 2014
5
0
0
XT1058 Root Clarification, Phone Suggestions...

Greetings.

I'm thinking about buying an AT&T XT1058.

I was looking at these phones last year, but we were still in the age of the locked boot loader. I absolutely despise branding and other limitations so I want full root.

Now it looks like I can root this phone and install CM... without any issues, or can I?

Is there any reason that I should NOT get this phone? Would an XT1060 be a better choice? Another model? I know that a developer edition or 2014 "Pure" would be easier to deal with, but I can't afford that right now (Lots of cheap xt1058s out there).

Thanks a ton in advance for any info, opinions, snark, sarcasm, litotes or other input. :laugh:
 

nimd

Member
Aug 4, 2013
14
0
0
Bricked my Moto X 2013 while flashing custom rom

My Moto X 2013 was a locked device i.e. its bootloader was locked. I initially unlocked my bootloader successfully and also rooted it, with twrp recovery installed without any problems. While flashing it with a custom ROM, I flashed it with a wrong firmware. Now its hard bricked. Cant boot normally, cant boot into recovery, nothing. I followed the unbricking tutorial. However I am getting the following error:

RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000

Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000

Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
sdl_hello() - Invalid response: 7e030003331b7e
sdl_hello() - This is a NAK response from ROM code, which means the device has
been reset back to blank flash mode. Usually this is caused by power supply issues. Please try again with battery eliminator if it persists
Unexpected target reset, bailing out after 2 retries


Does this error indicate a hardware damage? Is my device truly dead? Can I do anything to solve the issue??? Please help guys.
 
Last edited:

nimd

Member
Aug 4, 2013
14
0
0
I checked with rsd lite...it says:

Device Properties:
ESN:
Technology: N/A
Software version: N/A
Flex Version: N/A
Bootloader Version: N/A
DRM Version: N/A

Can I do anything to flash a new bootloader into my Phone??
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone