Database Develop

4.2.2 to 4.4 Root Nightmare

So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!

HTC-OH_SNAP said:
So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!
Click to expand...
Click to collapse
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.

kj2112 said:
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.
Click to expand...
Click to collapse
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.

HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.

kj2112 said:
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.
Click to expand...
Click to collapse
The Safestrap process, and installing a proper safestrap rom does not update the phone's bootloader. I think it also doesn't touch the GPT.BIN.
I know you haven't had experience with Safestrap, so think of it as kind of a Host OS/Guest OS setup, or if it was a PC then kind of like a Virtual PC setup where you could have a PC running real Windows 7 on your C drive that you boot too, plus having Windows 8 in a virtual PC and the Virtual PC's image file being stored on your "D drive". Installing W8 in the virutal PC doesn't touch the W7 "host" os, or its boot partition, etc. (its not 100% exactly the same, but that is the best analogy I can come up with at the moment).
---------- Post added at 06:35 AM ---------- Previous post was at 06:02 AM ----------
HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
re: safestrap affecting the bootloader, no, it does not. At least if you are using a ROM made for safestrap, and properly follow the process.
To determine the bootloader version, boot the phone to bootloader mode it should show the version number. I believe 30.B4 is 4.4.2 and 30.71 is 4.4 and 4.2.2 w/camera fix. As @kj2112 has mentioned, If the bootloader has been updated to 4.4.2, do NOT attempt to downgrade. However when using safestrap properly, its different.
As for the error at step 3... apparently it is common for those who had once used MotoWpNoMo to disable write protection, then trying to run though the SlapMyMoto process.
The actual process for getting a working Safestrap setup is the same for all Moto X's, however the Safestrap roms, and possibly the installer, are model specific... So, for example, if you have a Verizon X with locked bootloader, you could still follow [GUIDE] Republic Wireless Moto X KitKat 4.4.2 Root, Safestrap, TWRP, and MotoWpNoMo but using the Verizon specific SBFs, SafeStrap and Safestrap Roms instead of the ones for T-Mobile and RW linked in that thread (like on steps 1b, 3a, 5a, 6b).
Because of that, I'll point you to -> http://forum.xda-developers.com/showpost.php?p=52401229&postcount=30 as it is the quickest link I can find to a work around for slapmymoto if you've already disabled write protection with MotoWpNoMo.
I'm sure if you took the time to read every post in the SlapMyMoto thread or the entire MotoWpNoMo thread you will likely find discussions about your situation and a fix. For example: Post 349 through 357 of the MotoWpNoMo thread is a user having the same issue, but later says it was due to the SlapMyMoto file being the older 0.5c version rather than 1.0.
I'm sorry, I'm just not good with RockMyMoto/SlapMyMoto/MotoWpNoMo/etc and Safestrap as I have an unlocked bootloader, so I never had to mess with them to root and disable write protection.

how do i spf back to 4.2.2?

coolguy71261 said:
how do i spf back to 4.2.2?
Click to expand...
Click to collapse
This is someone's thread with their particular issue. If we start helping you in this thread with your issue....that is called thread hijacking.
You need to ask in a thread relevant to your issue, or start a new thread.
However.....since we don't know anything about your situation or your issue.....advice is hard to give.
You can probably start here tho.... http://forum.xda-developers.com/showthread.php?t=2603358
If that doesn't help, you need to make your own thread. And be as specific as possible with the details. But only start a thread if searching comes up with nothing and no existing threads match your issue.
Just some XDA etiquette.
Good luck.
And sorry to OP for off topic.

If you rooted with rockmymoto and took write protection off. You'll still have it so the only process you'll need to do is slapmymoto on 4.4. Safestrap will work with 4.2.2 and 4.4. If you want root stay there don't go to 4.4.2
MOTO X

KidJoe said:
Great Advice
Click to expand...
Click to collapse
Ok... so here is how the whole thing ended.
Checked my Bootloader - it was still 30.71.
Verified I still had Write Protection off.
Ran SlapMyMoto 1.0.
Took the OTA (From 4.2.2 it is still 4.4 and NOT 4.4.2)
Ran the ADB Shell Commands.
Installed SuperSu from the Play Market, and...
Rooted 4.4 with Write Protection Off.
Thanks!

[Q] Updating DIRECTLY from 4.2.2 to 4.4.3 (Unlocked+Rooted)

So here's the deal, I unlocked my T-Mobile Moto X bootloader through Motorola's website about a year ago or so. I also rooted and didn't bother updating afterwards to anything since I had everything working perfectly for me. Now I need to update my 4.2.2 Moto X to 4.4.3 (or really anything >=4.3 just so I can use my Moto 360 that'll be arriving soon).
My question is, with an unlocked bootloader, rooted, TWRP 2.6.3.1, Xposed-installed Moto X, can I go ahead and flash a stock 4.4.3 ROM (for example from here: http://forum.xda-developers.com/moto-x/development/rom-stock-flashable-t-mobile-t2773675) and just call it a day?
I've been reading past threads and stuff to get back into the loop, but I just can'f find anything to answer me the simple question of updating an unlocked+rooted 4.2.2->4.4+ while keeping root. Just the simple question of, if I get a stock 4.4 image and flash it on my phone, will everything be okay?
I no longer have the passion and interest to constantly be fiddling with kernels, ROMs, and little hacks with my phone like I used to with my OG Droid and, to a lesser extent, with my Galaxy Nexus (plus I feel like it's gotten significantly less easy since those OG days).
I know (i.e. 90% sure) that one way to do what I want (kinda) is RSDLite/manually go back to stock without root on 4.2.2 and then accept the OTA, but certainly it has to be easier than that right? What happened to the days where I can just find a new Gingerbread ROM for my Froyo Droid and just flash it right then and there? Now everything is "go back to stock and do these convoluted steps."
(I'm sorry I'm ranting, I'm just really tired at the moment haha)
Thank you all, hopefully, for the help!

If you don't care about retaining your data, grab the 4.4.3 fxz and unzip it. Follow the directions for returning back to stock here: http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358 but replace the files to be flashed with the files from the 4.4.3 fxz. Not sure where you got the idea that you need to go back to stock. Word of caution, once on 4.4.3 there's no going back to an older version.

I have the same question as the OP, on unlocked rooted 4.2.2 ATT Moto X, can i flash a custom 4.4.4 and keep root?

RGNDI said:
I have the same question as the OP, on unlocked rooted 4.2.2 ATT Moto X, can i flash a custom 4.4.4 and keep root?
Click to expand...
Click to collapse
You can take the ota but you need the stock recovery. Since you are unlocked you will not lose your unlocked-ness(lol) if you take an ota. But you do need to be completely stock: no su, no custom recovery, etc etc. But once you upgrade to 4.4.3 getting root back is as simple as flashing the appropriate version recovery again and then flashing supersu.

1ad_m12 said:
You can take the ota but you need the stock recovery. Since you are unlocked you will not lose your unlocked-ness(lol) if you take an ota. But you do need to be completely stock: no su, no custom recovery, etc etc. But once you upgrade to 4.4.3 getting root back is as simple as flashing the appropriate vision recovery again and then flashing supersu.
Click to expand...
Click to collapse
OK thanks, but cant I just Flash a Rooted Stock 4.4.4 over 4.2.2? Thats a more to the point question

RGNDI said:
OK thanks, but cant I just Flash a Rooted Stock 4.4.4 over 4.2.2? Thats a more to the point question
Click to expand...
Click to collapse
Yeah that would work as long as your radio is compatible with the rom. The rom you shared earlier should be fine. Just don't downgrade to anything pre 4.4 as that can cause issues because of partition sizes (or so I've heard). But after that I wouldn't take any OTA's cause your bootloader would be incompatible with the OTA and possibly cause a brick. If I were you I'd revert to stock and take the long way to 4.4.3 just so I can get the OTA for when Android L comes out. In fact thats what I plan on doing if the Sunshine bootloader unlock is successful. But if you don't care about that then everything should be fine.

How to root UK moto x (xt1052)

Hi there, I have a UK moto x model xt1052. I am looking to root and flash custom ROMs onto my device, but am concerned that I will brick the device by using a method intended for a different model of moto x.
The UK moto x was shipped with android 4.4.2, later updated to 4.4.4 so there are no earlier builds of android to downgrade to.
Any help will be appreciated.
Timsteels

Figure out if you can, and want to unlock your bootloader.... Then go to the One Stop Shop root thread sticky at the top of the general section. It has all your options.
---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------
And root methods have nothing to do with your model. It mostly has to do with locked or unlocked bootloader state.

timsteels said:
Hi there, I have a UK moto x model xt1052. I am looking to root and flash custom ROMs onto my device, but am concerned that I will brick the device by using a method intended for a different model of moto x.
Click to expand...
Click to collapse
Process to root the X is the same whether you have an XT1052, XT1053, XT1056, XT1060, etc. As KJ said, with 4.4.4 its all about can you unlock your bootloader or not. (and do you mind voiding your warranty doing so since you don't have a Developer Edition X).
See the One Stop Shop thread, in particular this post -> http://forum.xda-developers.com/mot...-confusion-t2826159/post54671918#post54671918
timsteels said:
The UK moto x was shipped with android 4.4.2, later updated to 4.4.4 so there are no earlier builds of android to downgrade to.
Click to expand...
Click to collapse
And you do NOT WANT TO DOWNGRADE!!!!! Doing so you will risk bricking your phone now, or when you later take an OTA. There are many warnings posted in the forums to not downgrade, and many threads started by those who have ignored the warnings and tried to downgrade and have bricked their phones!!!
Besides that, two key parts, GPT.Bin (partition table), and Motoboot.img (contains bootloader, TZ and a few other parts) will NOT downgrade successfully once on 4.4.2, 4.4.3 or 4.4.4. so any past exploits requiring the older roms wont work anyway.

So unlocking the boot loader is the same process as the us variants of the moto x? I just don't want to turn my phone into a paperweight! I'm not too worried about the warranty, as I am usually careful with my phones.

Unlocking and recovery and ROOT is all the same on any X. What matters is Android version (cause locked 4.4.4 guys can't root in any way), locked or unlocked bootloader and that's about it.
An unlocked X is the same no matter a Dev Edition or any other. All the same.
As far as bricking... The only time that's a giant threat is trying to downgrade. Not saying an X has never been bricked another way, cause everything we do has some risk to it. But most issues are curable.

Ok thanks for the info! And in terms of custom roms, do I need to install one built for the xt1052, or will other ones also work?

That is not something I know about. Never flashed one. Just stock and gravity box.
Read the opening post of rom threads, should have what devices it's for. ?

Ok thanks again! Is there much point in installing the exposed framework or anything similar?

I think many rooted X members here use Gravity Box while on stock rom... So they can customize some things. ?

Ok cool. I will have a look and decide if I want to go ahead. Thanks for all the assistance

timsteels said:
Ok thanks again! Is there much point in installing the exposed framework or anything similar?
Click to expand...
Click to collapse
Many root, install Xposed and some modules to customize their phone rather than running any Custom Roms because the custom roms often lose the Moto features like the notifications and such.

Ok and if I root, unlock bootloader and install xposed, will my phone still receive the ota updates? Or is it a case of reversing the procedure to get the ota updates?

timsteels said:
Ok and if I root, unlock bootloader and install xposed, will my phone still receive the ota updates? Or is it a case of reversing the procedure to get the ota updates?
Click to expand...
Click to collapse
First you can't install an OTA with a custom recovery (like TWRP, CWM, Philz) on the phone. You'll get stuck in a boot loop.
Next, in every OTA there is a "pre-validation check" (a manifest file which contains a list of items to be checked and a SHA type hash code for a type of check sum verification of each part/file its looking at.)
Anything that alters your phone from what the Pre-Validation check is looking for will cause the OTA to fail. So if you modify or remove and system files, have the wrong recovery, etc., those parts would not pass the pre-validation check so the OTA would fail.
Xposed also needs to be disabled, or it will cause the OTA's pre-validation checks to fail.
So it really comes down to what you do after you root.
If you flash TWRP, Root, install Xposed and a few modules, and nothing else, then to take an OTA, you'll need to disable Xposed (there is a flashable zip on your /SDcard to do this), then flash stock recovery.img back on your phone, then you can take the OTA. Once the OTA is successfully installed, you can re-flash custom recovery, re-root if necessary, and re-enable Xposed.
If you rename/delete/modify files from /system (like some do to get rid of bloat), you'll need to un-do that.
If you're like me, I just unlocked, rooted, and installed apps that use root (like Root Explorer, Greenify, Wifi Tether for root), so all I do is flash stock recovery on, take the OTA, and if I lost root, flash TWRP and re-root.
For more see -> http://mark.cdmaforums.com/MotoX-OTA.html

Ok that's good to know. I'll have a think about it. I may wait until lollipop comes out for the moto x.

[Q] XT1053 4.4.4 Root?

Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;

stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358

You'll have to unlock the bootloader. No way around it.

Should I be nervous about unlocking the bootloader?
Didn't my Samsung phone come with it already unlocked?

Should you be nervous? Google the pros and cons then decide for yourself.
No phone nor tablet comes with an unlocked bootloader.

I have an XT1053 and just recently unlocked the bootloader through the Motorola site. I waited until now because my original warranty just expired and knew that unlocking the bootloader would void my warranty. I wanted to unlock the bootloader under 4.4.4 because I didn't know if there would be any problems once Lollipop was offered as an update. The unlock process went very smoothly and took only a few minutes. You probably already know that unlocking wipes your phone, so be prepared to reinstall apps and other files. I have not rooted yet because I'll probably wait to do that after the Lollipop OTA comes around. Even then, I may not root because I'm really pretty happy with the phone as it is. For me, unlocking the bootloader was just of way of preserving the future option to root.

stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app

mac1996 said:
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4

stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
Do you have fastboot?
if yes, go to your phone bootloader.
Connect to your computer by USB.
Type the following in cmd. (place your recovery img file in fastboot directory)
fastboot flash recovery (your recovery name).img
Sent from my XT1053 using XDA Free mobile app

Check the sticky threads. There's only a year and halfs worth of information available to you here and all over the rest of the internet.

stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
At any point after unlocking the bootloader... To flash recovery, did you do the following...
Start the phone in Fastboot/Bootloader mode.. then from the PC type...
mfastboot flash recovery YourRecovery.img
mfastboot reboot-bootloader
Follow onscreen directions to use vol down key and highlight recovery, then use vol up to select/enter recovery. Once in recovery you can reboot the phone and proceed with whatever you want.
Failure to reboot-bootloader and entering recovery immediately after flashing recovery (i.e. doing something else first) can result in the recovery not sticking.

4.4.4
a year old post by dray_jr says the following:
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
can someone explain this to me? I got my phone around august 2014, it came with 4.4.3 and right now I'm on 4.4.4.
If I use the motorola website and follow their bootloader unlock steps am I fine? will I have any brick issues stated from the quote above?

Thread
Nevermind guys, found the perfect thread for 4.4.4 root!
Thread: http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Final question: I don't have to install supersu root if i install CM12 once i get into TWRP recovery am i correct? (since cms come rooted)

Would flashing a JB kernel (and only the kernel) work to root it as described here?: http://forum.xda-developers.com/crossdevice-dev/sony/guide-xperia-kitkat-4-4-4-rooting-t3003520

Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?

nhizzat said:
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
Click to expand...
Click to collapse
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...

dagoban said:
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
Click to expand...
Click to collapse
I don't proclaim to know the ins and outs of all things android, but I do know this.. Just because a phone has android 4.4.4 doesn't mean its the same 4.4.4 with the same exact flaws and vulnerabilities, susceptible to the same exact root processes. Its why an exploit to root one phone, often doesn't work to root another.
In the case of the Moto X with a locked bootloader, JCASE has come out with many processes exploiting vulnerabilities for Android and the Apps on the Moto X to not only root it, but disable its write protection. As new OTA's have patched an exploit, he came out with other ways.
Starting wth 4.4.2, the vulnerability in the bootoader to disable write protection has been patched.
Jcase's Sunshine tool works on the X with 4.4.3 and lower, and only SOME with 4.4.4. It needs temp root first, etc. For whatever reason, we don't have a way to even temp root the 2013 X on 4.4.4 enough to allow Sunshine to do its work. And despite being asked many times, Jcase pretty much said in the Sunshine discussion threads that v3.0 wont have Moto X 4.4.4 support (unless he changed his mind and I missed it). Yet sunshine and its root processes, etc work on other phones (HTC) with 4.4.4.
But back to the thread you link...
On the X, due to its security measures, with a locked bootloader, you can only flash the Moto signed ROM for your phone. Nothing else. Because of this, you can't flash a custom recovery. To flash items, we use mFastboot and RSDLite. They need the img files, or bin files. If we make our own, they wont be signed, so they wont flash to a phone with a locked bootloader. And you can't package them into a flashable ZIP because stock recovery looks for the Moto digital signature (which we don't have and can't fake), and you can't install TWRP/CWM/Philz/etc to flash that way. So if you manage to pull the JB kernel out of the Moto SBF file, you wont be able to flash it.
Due to write protection on the 2013 X, any changes made to /System and a few other places, will be lost at power off/on. In other words, if you do manage to flash it (or push via adb), it wont stick due to write protection.
We've seen people try and manipulate their phone by trying to DOWNGRADE their ROM. Well, this doesn't work either. GPT.BIN (partition table), and Motoboot.img (bootloader, TZ, and a few other things) get in the way. Even on an X with an Unlocked bootloader, you can't downgrade these parts. Enough who attempted this have ended up bricking their phone immediately, or with later taking an OTA. Sure you can try to flash just system.img, and while that has less risk for bricking, people who have tried this were still not able to use the older Root Exploits (that worked if you hadn't upgraded already). People have tried flashing everything but GPT.BIN and MotoBoot.img. Again, it didn't help with rooting. Not to mention with a missmatched system.img or other parts, features on the phone may not always work properly (going Settings -> Security comes to mind), and you are at risk of bricking should you take an OTA update.
Since that process exploits a vulnerability, and its out there (so the vulnerability is in the public), I'm sure if it worked or was possible, JCASE, Beaups, or others would have put something together.
Now, back on topic of the XT1053... it has an Unlockable bootloader. Unlocking the bootloader disables write protection, and allows you to flash non-moto stuff. So unlocking the bootloader, flashing TWRP, reboot bootloader, enter TWRP and root, is quick, easy, effective, and doesn't rely on vulnerabilities on the phone to be exploited so patches/updates haven't got in the way. Plus you don't have to wait for someone to find them and create a repeatable process.

Advice on Updating Device

Hi All,
I'm still rocking my 2013 Moto X XT1060 as my daily device. It's currently on 4.4, rooted, unlocked bootloader, stock rom with exposed framework. i disabled the OTA updates on it because at the time, I didn't have an unlocked bootloader and didn't want to loose root (I'm not on the dev-edition). Anyway, my bluetooth has started to crash and want to/should update 4.4.4 or 5.1. What do you recommend?
In addition to that, what method should I use to get there:
1. SFB back to 4.2.2 (I'm currently on 4.4 so I don't think that shouldn't be a problem but please tell me otherwise)
1a. Take all the OTAs to 4.4.4 or 5.1?
2. SFB to 4.4.4 (directly from 4.4, not sure if that's a problem)
3. SFB to 5.1 (directly from 4.4, again, not sure if that's a problem)
Thank you!

If it were me, I would take the 4.4.4 update and stop there. I have mine rooted with stock 4.4.4, and everything just works. Kit kat is really the sweet spot for this phone.

Thanks! What method should I take to get there? Can I SBF directly to it from 4.4 or is it possible to downgrade back to 4.2.2 from 4.4 and take the updates? I've been out of the scene since I got the phone back in 2013 so I can't remember if downgrading to 4.2.2 is OK.

You should not downgrade to 4.2.2, besides it's not necessary. If you want to get to 4.4.4, then I would use the method compiled in this post by liveroy. It's not complicated, simply follow the directions exactly. I then reflashed TWRP recovery, and installed SuperSU, in order to use AdAway and ES File Explorer's root access. If you want to remain stock, then omit TWRP and SuperSU.
http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118
Note: as suggested by KidJoe, I used TWRP 2.8.6.0 and the most recent SuperSU.

wmdunn said:
If it were me, I would take the 4.4.4 update and stop there. I have mine rooted with stock 4.4.4, and everything just works. Kit kat is really the sweet spot for this phone.
Click to expand...
Click to collapse
Agreed. I kept KK while my friends upgraded to 5.1, nothing but problems and extremely poor battery life.