Database Develop

[Q] What root path do I use?

I just got a Moto X (non-developer edition) and I'm looking to root to take advantage of Xposed and Gravitybox. I'm a little confused as to what path to take however. I'd like to be able to get to 4.4 and still retain OTA updates without losing root, if possible.
Here's my details:
VZW Moto X
Android 4.2.2
Baseband MSM8960PRO_BP2323.020.90.00R
System: 139.15.1.ghost_verizon.verizon.en.us
Build Number: 13.9.0Q2.X-116-MX-17-57-X-1

You will need to look at using the SlapMyMoto method.
But you will not be able to take the future OTAs until someone figures out how to root them (if it even can be done).

I thought that the Slapmymoto method was from the 4.4 OTA already? Should I take the OTA and follow from step 1 of the guide? Or can I just skip downgrading and follow all the way through?

pan2thada said:
I thought that the Slapmymoto method was from the 4.4 OTA already? Should I take the OTA and follow from step 1 of the guide? Or can I just skip downgrading and follow all the way through?
Click to expand...
Click to collapse
If you are on 4.2.2 currently, just start the slapmymoto process as if you have just freshly flashed back to 4.2.2.
The Slapmymoto process will take you up to 4.4 and be rooted.
What mjphillips1981 was saying is once you use Slapmymoto, you will not be able to take any future OTA updates. If Slapmymoto works anything like the previous generation roots, it replaces your stock recovery, and some other things that will make OTA updates fail, lose root, and possibly cause you to be stuck in a boot loop (which should be repairable).
Just like other phones, when future ROM updates come out, unless you have an unlocked bootloader, you need to wait for someone to find an exploit, take advantage of it, and bring out a repeatable root process. So once you root, if you want to keep root, do NOT take an OTA until a root exploit and process have been posted.

KidJoe said:
If you are on 4.2.2 currently, just start the slapmymoto process as if you have just freshly flashed back to 4.2.2.
The Slapmymoto process will take you up to 4.4 and be rooted.
What mjphillips1981 was saying is once you use Slapmymoto, you will not be able to take any future OTA updates. If Slapmymoto works anything like the previous generation roots, it replaces your stock recovery, and some other things that will make OTA updates fail, lose root, and possibly cause you to be stuck in a boot loop (which should be repairable).
Just like other phones, when future ROM updates come out, unless you have an unlocked bootloader, you need to wait for someone to find an exploit, take advantage of it, and bring out a repeatable root process. So once you root, if you want to keep root, do NOT take an OTA until a root exploit and process have been posted.
Click to expand...
Click to collapse
Thanks! I'm coming from first a HTC Incredible and then a GNex so I'm not used to not being able to unlock the bootloader... I'm a little confused about these steps however:
Wait for the bootlaoder screen to appear
Code:
fastboot flash recovery recovery.img
fastboot reboot
Once the device has rebooted, go ahead and take the OTA, once 4.4 is up and running continue.
Step 5)
Now we need to downgrade the bootloader using the 4.2.2 bootloaders and flash the normal kernel to the recovery partition:
Code:
adb reboot bootloader
Wait for the bootlaoder screen to appear
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot reboot
Step 6)
Once booted into 4.4,
Code:
adb push su /data/local/tmp/su
adb push install.sh /data/local/tmp/install.sh
adb push rec.sh /data/local/tmp/rec.sh
adb push install-recovery.sh /data/local/tmp/install-recovery.sh
adb push setup.sh /data/local/tmp/setup.sh
adb reboot
Click to expand...
Click to collapse
First, does the fastboot flash command make a backup of my bootloader? If not, where do I get the bootloader I'm re-downgrading to from? Also where do the recovery.img or motoboot.img files come from? I just want to make sure I fully understand the process before I accidentally brick my phone.

KidJoe said:
If you are on 4.2.2 currently, just start the slapmymoto process as if you have just freshly flashed back to 4.2.2.
The Slapmymoto process will take you up to 4.4 and be rooted.
What mjphillips1981 was saying is once you use Slapmymoto, you will not be able to take any future OTA updates. If Slapmymoto works anything like the previous generation roots, it replaces your stock recovery, and some other things that will make OTA updates fail, lose root, and possibly cause you to be stuck in a boot loop (which should be repairable).
Just like other phones, when future ROM updates come out, unless you have an unlocked bootloader, you need to wait for someone to find an exploit, take advantage of it, and bring out a repeatable root process. So once you root, if you want to keep root, do NOT take an OTA until a root exploit and process have been posted.
Click to expand...
Click to collapse
But you can always SBF back to factory stock to be able to get OTA's again, right? Without root anymore of course.

detonation said:
But you can always SBF back to factory stock to be able to get OTA's again, right? Without root anymore of course.
Click to expand...
Click to collapse
Yes.

detonation said:
But you can always SBF back to factory stock to be able to get OTA's again, right? Without root anymore of course.
Click to expand...
Click to collapse
In the current state. Yes. That is one way to fix the "boot loop" issue I mentioned, and get back to stock.
i.e. if you are on KK and root, you can re-flash the same KK rom and get back to stock and take a future OTA, without root.
---------- Post added at 03:07 PM ---------- Previous post was at 02:58 PM ----------
pan2thada said:
First, does the fastboot flash command make a backup of my bootloader? If not, where do I get the bootloader I'm re-downgrading to from? Also where do the recovery.img or motoboot.img files come from? I just want to make sure I fully understand the process before I accidentally brick my phone.
Click to expand...
Click to collapse
These questions are answered in the Slapmymoto thread but..
No, the fastboot flash command does NOT backup anything... it FLASHES the files stored on your PC onto your phone. For example: Fastboot flash recovery recover.img would flash the recovery.img on your PC to your phone's recovery "partition"
and looking at the steps, Step 1 tells you to flash back to 4.2.2, which you are on. BUT you still need to download and unzip the 4.2.2 rom for your phone (step 1 has links to the Verizon and ATT versions), as that is where you'll get the .IMG files, logo.bin and other files you'll need in step 4 and 5.
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools

KidJoe said:
In the current state. Yes. That is one way to fix the "boot loop" issue I mentioned, and get back to stock.
i.e. if you are on KK and root, you can re-flash the same KK rom and get back to stock and take a future OTA, without root.
---------- Post added at 03:07 PM ---------- Previous post was at 02:58 PM ----------
These questions are answered in the Slapmymoto thread but..
No, the fastboot flash command does NOT backup anything... it FLASHES the files stored on your PC onto your phone. For example: Fastboot flash recovery recover.img would flash the recovery.img on your PC to your phone's recovery "partition"
and looking at the steps, Step 1 tells you to flash back to 4.2.2, which you are on. BUT you still need to download and unzip the 4.2.2 rom for your phone (step 1 has links to the Verizon and ATT versions), as that is where you'll get the .IMG files, logo.bin and other files you'll need in step 4 and 5.
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools
Click to expand...
Click to collapse
can i use this fastboot installer?
http://forum.xda-developers.com/showthread.php?p=42407269

pan2thada said:
can i use this fastboot installer?
http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
that is a minimal install of Android SDK/Platform tools. Yes you can start with that... BUT you still need to use the special motorola fastboot.exe that I linked to instead of the stock fastboot.exe part of the package in this thread you are linking to.

KidJoe said:
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools
Click to expand...
Click to collapse
KidJoe said:
that is a minimal install of Android SDK/Platform tools. Yes you can start with that... BUT you still need to use the special motorola fastboot.exe that I linked to instead of the stock fastboot.exe part of the package in this thread you are linking to.
Click to expand...
Click to collapse
I used the Android SDK/Platform tools fastboot.exe without issue to root my VZW Moto X using SlapMyMoto. Knowing what I know now, I wouldn't recommend it. Just saying it can be done.

KidJoe said:
In the current state. Yes. That is one way to fix the "boot loop" issue I mentioned, and get back to stock.
i.e. if you are on KK and root, you can re-flash the same KK rom and get back to stock and take a future OTA, without root.
---------- Post added at 03:07 PM ---------- Previous post was at 02:58 PM ----------
These questions are answered in the Slapmymoto thread but..
No, the fastboot flash command does NOT backup anything... it FLASHES the files stored on your PC onto your phone. For example: Fastboot flash recovery recover.img would flash the recovery.img on your PC to your phone's recovery "partition"
and looking at the steps, Step 1 tells you to flash back to 4.2.2, which you are on. BUT you still need to download and unzip the 4.2.2 rom for your phone (step 1 has links to the Verizon and ATT versions), as that is where you'll get the .IMG files, logo.bin and other files you'll need in step 4 and 5.
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools
Click to expand...
Click to collapse
Thanks, unfortunately the Slapmymoto thread is 80 pages long and growing, so it's hard to get anything useful out of it. This is what I thought I was supposed to do but I wasn't certain.

[Q] Bricked my Moto X - can I resurrect it?

My Moto X now refuses to boot. With stock recovery it'll get past the bootloader, then blink an image of a dead android with the message "Error" briefly, and keep doing so every ~10 seconds. If I flash TWRP, any attempt to boot takes me to TWRP, with log messages reading "unable to mount..." for a bunch of partitions (/data, /cache, storage, etc.)
Can I recover my device?
The short sequence of events: I rooted my phone (T-Mobile phone, unlocked it via Motorola's website) and installed TWRP. Later I tried to accept the 4.4.2 OTA update, but the phone wouldn't take the update, because TWRP. Flashed stock recovery tried again, got stuck in bootloop. Tried flashing back the 4.4 / 140.44.3 images from here, now I'm stuck with a blinking error message.
I see there are a bunch of image files bundled into the 4.4.2 / 161.44.25 update - would flashing those do any good?

What version is your bootloader?

Steve-x said:
What version is your bootloader?
Click to expand...
Click to collapse
Version 30.B2.

OK, you still have the 4.4 bootloader so you should have no problem flashing the full tmobile/retail/dev edition build of firmware. I'd perform a full flash with rsdlite or with fastboot using all of the commands in the xml file in the same order. Do not skip any files or bypass any files if there are errors.
This will reset your phone and wipe all content!

Did you attempt to clear dalvik and cache, I believe you can do it through fastboot
Fast boot erase cache should work . its trying to flash the it's ,so you need to delete the cache where the ota file downloaded to
Sent on my Gummy running Lenoto X

so here is abit more help here are the full firmware links
T-Mobile 4.4
http://sbf.droid-developers.org/download.php?device=0&file=2
that is the file you need to flash with RSD Lite or Fastboot and it should get you 100% back up and running.
But then if you want to go to 4.4.2 after you flash the firmware before you add anything or install TWRP just update the phone to 4.4.2 then install the custom recovery and SuperSU.

Steve-x said:
OK, you still have the 4.4 bootloader so you should have no problem flashing the full tmobile/retail/dev edition build of firmware. I'd perform a full flash with rsdlite or with fastboot using all of the commands in the xml file in the same order. Do not skip any files or bypass any files if there are errors.
This will reset your phone and wipe all content!
Click to expand...
Click to collapse
I have tried both RSD Lite, and applying all of the commands from the XML file manually, following the directions from here. Both ways, I still get the blinking error message

The "can't mount..." log messages I get if I flash back to TWRP suggest it could be some sort of partitioning problem, but I'm not sure how to diagnose that.

And the flashing of all files completes successfully?

Steve-x said:
And the flashing of all files completes successfully?
Click to expand...
Click to collapse
I could have sworn that I wasn't getting any errors previously. Now, however, after trying to flash system.img (making sure to use mfastboot, of course), I get an error on the phone, "sp space is not enough". Not sure what it means, and Googling around doesn't turn up any answers.

dray_jr said:
so here is abit more help here are the full firmware links
T-Mobile 4.4
http://sbf.droid-developers.org/download.php?device=0&file=2
Click to expand...
Click to collapse
Yep, that's exactly what I flashed. Made sure the md5sum matched my download and everything.
flashallthetime said:
Did you attempt to clear dalvik and cache, I believe you can do it through fastboot
Click to expand...
Click to collapse
Yep, cleared the cache, no luck

Ouch, it does kind of sound like the partition table got damaged. I suppose you could try "fastboot erase system" and then try to flash the system partition again.

So I guess more warnings into my noobs guide to accept an ota thread
Maybe I should put a notice not to accept the ota and only flash your carriers sbf firmware when available?
Sent on my Gummy running Lenoto X

Steve-x said:
Ouch, it does kind of sound like the partition table got damaged. I suppose you could try "fastboot erase system" and then try to flash the system partition again.
Click to expand...
Click to collapse
Code:
C:\Users\spiffytech\Documents\sdk\platform-tools>fastboot erase system
(bootloader) Variable not supported!
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.101s

Well, that was very weird. In the bootloader I scrolled through the menu and accidentally selected "Factory". No idea what that's supposed to do, but now my phone boots again! I'm going to really, really, hope I don't break it again...
I want to try the 4.4.2 update now, but given I'm not really sure why my device works again I'm scared to.

spiffytech said:
Well, that was very weird. In the bootloader I scrolled through the menu and accidentally selected "Factory". No idea what that's supposed to do, but now my phone boots again! I'm going to really, really, hope I don't break it again...
I want to try the 4.4.2 update now, but given I'm not really sure why my device works again I'm scared to.
Click to expand...
Click to collapse
Good for you, I would wait for the sbf firmware to be available to flash, seems to me a safer way of getting the update
Sent on my Gummy running Lenoto X

flashallthetime said:
Good for you, I would wait for the sbf firmware to be available to flash, seems to me a safer way of getting the update
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'll go with that plan What is it that makes flashing from sbf safer?

So if you perform a full factory reset the phone will boot up normally now? If that is the case then I don't see any problem with accepting the OTA to 4.4.2.

Help PLZ
I had the exact same problem as OP, took the same course of action, and got a successful boot. I do some minimal stuff, check if everything is working, turn on dev mode, etc. I put in my wifi password.
I wanted to check if my bootloader was back to stock, so I turned off my device, and then tried to power on. Pressing the power button does nothing.
So I get into fastboot, and select factory (reset) again. It boots up, but it doesn't seem like it actually did a factory reset, because it automatically connected to my wifi..
Have you any idea what's going on, and how perhaps to solve this weird dilemna?
EDIT: I'm not sure if I actually did anything, but after a couple reboots it just started working normally. I installed the update to 4.4.2 and everything is smooth thus far.

Eventually the phone prompted me to apply the 4.4.2 update so often the phone was actually unusable - it'd go back to the "do you want to update?" screen as soon as I backed out of it. I was thus forced to apply it OTA. Fortunately, the update went through fine this time, and my phone continues to work fine
Thanks for your help, folks!

[Q] please help possible full brick

Hopefully someone is able to help...
I had my tmo moto x unlocked with twrp and root and I tried a factory reset through the twrp recovery and it erased all the software. It booted to the setup screen where I proceeded to log in with Google but it didn't work I think and when it got the home screen it just showed a loading circle and that's it and stupid me I didn't make a backup before
I've tried using the tool in the android development thread to flash back to stock but now my phone doesn't even boot at all I can get to the bootloadwr and I can successfully flash files through the Motorola tool by removing the proper line in the XML file but my phone still don't boot
It just flashes the little android laying down and says error every 5 seconds I don't know what to do anymore I've searched all over and no matter what I can't get the phone to boot
Thanks for the help if any

1. With an unlocked bootloader, you're not fully bricked if you can get to the bootloader.
2. Download the SBF file for your variant here http://sbf.droid-developers.org/phone.php?device=0. If you're already on the 4.4.2 bootloader, download only the 4.4.2 SBF file.
3. Learn how to use fastboot/mfastboot and adb. Follow the steps in the "return to stock" section here http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358.
4. Extract the SBF file, boot into the bootloader, type what's in the "return to stock" section verbatim. Skip the fastboot oem lock step though and don't copy/paste.
5. Stop using toolboxes and scripts until you understand how fastboot and adb work. They'll save your ass each and every time.

nhizzat said:
1. With an unlocked bootloader, you're not fully bricked if you can get to the bootloader.
2. Download the SBF file for your variant here http://sbf.droid-developers.org/phone.php?device=0. If you're already on the 4.4.2 bootloader, download only the 4.4.2 SBF file.
3. Learn how to use fastboot/mfastboot and adb. Follow the steps in the "return to stock" section here http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358.
4. Extract the SBF file, boot into the bootloader, type what's in the "return to stock" section verbatim. Skip the fastboot oem lock step though and don't copy/paste.
5. Stop using toolboxes and scripts until you understand how fastboot and adb work. They'll save your ass each and every time.
Click to expand...
Click to collapse
thank you so much for the help but for some reason when i flash the files to my device they run the process perfectly fine but when the phone boots its still doing the same thing where it just flashes the android on his back for like a second every five seconds or so. I did the 4.4.2 update first then i tried 4.2.2 just to give it a shot but i dont think that flashed right since its says an error about downgrading the security in the bootloader
please if there are any other suggestions im open ears ive searched everywhere and tried everything but i still cant get the phone to actually boot up at all
thanks for the help

genaro12543 said:
thank you so much for the help but for some reason when i flash the files to my device they run the process perfectly fine but when the phone boots its still doing the same thing where it just flashes the android on his back for like a second every five seconds or so. I did the 4.4.2 update first then i tried 4.2.2 just to give it a shot but i dont think that flashed right since its says an error about downgrading the security in the bootloader
please if there are any other suggestions im open ears ive searched everywhere and tried everything but i still cant get the phone to actually boot up at all
thanks for the help
Click to expand...
Click to collapse
once you've upgraded to 4.4.2, you can't go back to 4.2.2.
as mentioned, download the 4.4.2 fastboot files and flash each partition.
make sure to wipe data and cache once all partitions are flashed.
here are some more notes regarding flashing:
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682

[Q] Rooted 4.4.2 with locked bootloader factory reset safe?

Hi, I have a republic wireless moto x I just successfully rooted and updated to 4.4.2 from 4.2.2 with a locked bootloader with no write protection (wp)
Since I updated it to 4.4.2 I have this error that pops up that I can not resolve
"Unfortunately, the process com.motorola.process.system has stopped"
I googled several pages of several website results and several pages of google but can not find the solution.
Solutions found was to:
Safe Mode (I tried this first with no apps installed on non safemode and non system apps updated, didn't work and popped up even on safe mode)
Change date & time method (didn't work)
Wipe Cache (didn't work)
Wipe Cache & dalvik cache (didn't work)
I am debating about factory reset but unsure if it will make me lose my root because I have a locked bootloader (if that matters in anyway I am still new to this, and that my moto x is from republic wireless not like other carriers with unlocked bootloaders).
Please help me and discuss with me how I can get rid of that error.

androiddoglover6969 said:
Hi, I have a republic wireless moto x I just successfully rooted and updated to 4.4.2 from 4.2.2 with a locked bootloader with no write protection (wp)
Since I updated it to 4.4.2 I have this error that pops up that I can not resolve
"Unfortunately, the process com.motorola.process.system has stopped"
I googled several pages of several website results and several pages of google but can not find the solution.
Solutions found was to:
Safe Mode (I tried this first with no apps installed on non safemode and non system apps updated, didn't work and popped up even on safe mode)
Change date & time method (didn't work)
Wipe Cache (didn't work)
Wipe Cache & dalvik cache (didn't work)
I am debating about factory reset but unsure if it will make me lose my root because I have a locked bootloader (if that matters in anyway I am still new to this, and that my moto x is from republic wireless not like other carriers with unlocked bootloaders).
Please help me and discuss with me how I can get rid of that error.
Click to expand...
Click to collapse
You shouldn't have done it. You obviously didn't read or follow any of the guides here or you would have known better.
There was ONE (very tricky and convoluted) way of retaining root and it involves SafeStrap.
Sorry to say - there will likely be no root in your future.
A factory reset will most likely not help. You will have to download the 4.4.2 SBF and re-flash the entire stock rom.
There's a guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
^ This is the only way to get your phone back to being usable again. MAKE SURE you do NOT try to flash anything but 4.4.2. Flashing a prior version will likely permanently brick your phone.
After this process, the ONLY way you're going to obtain ROOT is to unlock your BL.
I hate to hear this happened to you, but its posted -all over- this forum that you cannot take the 4.4.2 OTA if you are rooted on a previous version. If you had followed the guide, and used Safestrap, you would be OK.....but now its too late. Once you've flashed the 4.4.2 OTA, it updates the bootloader, patching all of the exploits we used previously. Game Over.
Good Luck

samwathegreat said:
You shouldn't have done it. You obviously didn't read or follow any of the guides here or you would have known better.
There was ONE (very tricky and convoluted) way of retaining root and it involves SafeStrap.
Sorry to say - there will likely be no root in your future.
A factory reset will most likely not help. You will have to download the 4.4.2 SBF and re-flash the entire stock rom.
There's a guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
^ This is the only way to get your phone back to being usable again. MAKE SURE you do NOT try to flash anything but 4.4.2. Flashing a prior version will likely permanently brick your phone.
After this process, the ONLY way you're going to obtain ROOT is to unlock your BL.
I hate to hear this happened to you, but its posted -all over- this forum that you cannot take the 4.4.2 OTA if you are rooted on a previous version. If you had followed the guide, and used Safestrap, you would be OK.....but now its too late. Once you've flashed the 4.4.2 OTA, it updates the bootloader, patching all of the exploits we used previously. Game Over.
Good Luck
Click to expand...
Click to collapse
I did not have a root before 4.4.2. And I did not take the 4.4.2 OTA. I did follow the guide and have used Safestrap and still have it. What do you mean flash the 4.4.2 OTA? You mean installing it through the update notification? Well I didn't do that if that is what you meant. I flashed through the using the guide to get me no WP, root, and 4.4.2. So am I still doing it wrong?

androiddoglover6969 said:
I did not have a root before 4.4.2. And I did not take the 4.4.2 OTA. I did follow the guide and have used Safestrap and still have it. What do you mean flash the 4.4.2 OTA? You mean installing it through the update notification? Well I didn't do that if that is what you meant. I flashed through the using the guide to get me no WP, root, and 4.4.2. So am I still doing it wrong?
Click to expand...
Click to collapse
Sorry for the confusion...
Hmm...you didn't mention safestrap in OP - just that you "successfully rooted and updated to 4.4.2 from 4.2.2"
OK so if you followed the guide exactly your bootloader should still be on the JellyBean bootloader.
Assuming you followed the guide, you can start over. If you're ABSOLUTELY SURE you didn't update to the 4.4.2 bootloader, then I suggest starting from scratch.
Use RSD Lite to restore the 4.2.2 (JellyBean) rom (Again, you've been warned. If theres any possibility you flashed the 4.4.2 bootloader last time, this WILL brick your phone) Also, be careful to NOT flash the 4.4.2 ROM, or you will NOT be able to root as this patches the exploit.
Just follow the guide step-by-step: http://forum.xda-developers.com/moto-x/general/guide-republic-wireless-moto-x-kitkat-4-t2738233
The first step is to restore back the 4.2.2 stock rom, so this is where you should start. Don't forget to re-install safestrap and MotoWpNoMo as described.
Please let us know how it works out.
samwathegreat

samwathegreat said:
Sorry for the confusion...
Hmm...you didn't mention safestrap in OP - just that you "successfully rooted and updated to 4.4.2 from 4.2.2"
OK so if you followed the guide exactly your bootloader should still be on the JellyBean bootloader.
Assuming you followed the guide, you can start over. If you're ABSOLUTELY SURE you didn't update to the 4.4.2 bootloader, then I suggest starting from scratch.
Use RSD Lite to restore the 4.2.2 (JellyBean) rom (Again, you've been warned. If theres any possibility you flashed the 4.4.2 bootloader last time, this WILL brick your phone) Also, be careful to NOT flash the 4.4.2 ROM, or you will NOT be able to root as this patches the exploit.
Just follow the guide step-by-step: http://forum.xda-developers.com/moto-x/general/guide-republic-wireless-moto-x-kitkat-4-t2738233
The first step is to restore back the 4.2.2 stock rom, so this is where you should start. Don't forget to re-install safestrap and MotoWpNoMo as described.
Please let us know how it works out.
samwathegreat
Click to expand...
Click to collapse
Aslo, before I start to do the RSD Lite to restore the 4.2.2. Is there any other way how I can identify what is causing that error "com.motorola.process.system"? And isolate and get rid of that problem somehow or finding that stock app and preventing it from doing that?

androiddoglover6969 said:
Aslo, before I start to do the RSD Lite to restore the 4.2.2. Is there any other way how I can identify what is causing that error "com.motorola.process.system"? And isolate and get rid of that problem somehow or finding that stock app and preventing it from doing that?
Click to expand...
Click to collapse
Its extremely difficult to know why you are getting the error, but if you RSD Lite and start over, it will fix this issue.
Far too many people are running safestrap and not receiving the error. Likely there is a file on your device corrupted somewhere. RSD Lite will fix it as it completely restores the all of the partitions.
Just go -slow- step-by-step, and post here if you get confused or have questions. We will get your phone back to normal...
On another note....if you have $45 laying around, I highly suggest you email the gentleman from China. Once unlocked, you won't have to go through this long drawn-out process. You simply SBF back to stock, fastboot flash TWRP, and you're done. TWRP will install su-installer for you.
Your choice. The BL unlock method is best because you have permanent access and can never lose root.
Safestrap method will work as well, but you have to be very careful to not accept any new OTAs until the devs find a solution and post it here.
Good Luck.

samwathegreat said:
Its extremely difficult to know why you are getting the error, but if you RSD Lite and start over, it will fix this issue.
Far too many people are running safestrap and not receiving the error. Likely there is a file on your device corrupted somewhere. RSD Lite will fix it as it completely restores the all of the partitions.
Just go -slow- step-by-step, and post here if you get confused or have questions. We will get your phone back to normal...
On another note....if you have $45 laying around, I highly suggest you email the gentleman from China. Once unlocked, you won't have to go through this long drawn-out process. You simply SBF back to stock, fastboot flash TWRP, and you're done. TWRP will install su-installer for you.
Your choice. The BL unlock method is best because you have permanent access and can never lose root.
Safestrap method will work as well, but you have to be very careful to not accept any new OTAs until the devs find a solution and post it here.
Good Luck.
Click to expand...
Click to collapse
Woops I responded to another post but I am going to expect my bootloader code.
What is the first step from all of this that I should do?
1. SBF = what exactly? Hitting the factory reset button?
2. Fastboot Flash TWRP ? So after SBF. Fastboot Flash TWRP is done in AP Fastboot screen? Stock Recovery Screen? Or what screen exactly?
3. Did the guide I do didn't safestrap (twrp?) installed the su-installer for me as well right? Just wondering.

androiddoglover6969 said:
Woops I responded to another post but I am going to expect my bootloader code.
What is the first step from all of this that I should do?
1. SBF = what exactly? Hitting the factory reset button?
2. Fastboot Flash TWRP ? So after SBF. Fastboot Flash TWRP is done in AP Fastboot screen? Stock Recovery Screen? Or what screen exactly?
3. Did the guide I do didn't safestrap (twrp?) installed the su-installer for me as well right? Just wondering.
Click to expand...
Click to collapse
1.)
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
Download the correct file for your carrier and try to flash with RSD lite.
You can find a great guide here: http://forum.xda-developers.com/moto...using-t2446515
PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Basically, an SBF is a complete STOCK image of the original filesystem (all partitions). By SBFing, you will be 100% back to factory stock. This method (SBFing) will actually fix a corrupted filesystem.
A "factory reset" does NOT do this. I highly suggest you do the SBF back to stock, and not try just reseting. If there is corruption, reset won't fix it.
Don't bother setting up any apps yet or setting up the phone. Wait until you complete the entire process.
2.
Yes! You'll flash TWRP from the "AP Fastboot" screen (bootloader).
UNLOCK YOUR BOOTLOADER FIRST. Otherwise you won't be able to flash TWRP custom recovery.
Now unplug the USB cord, and power off your device. Hold down the VOL DOWN button, and power back on. You will now be in bootloader (fastboot) mode. Plug the USB back into the phone now.
You must have "mfastboot" downloaded. You'll type:
mfastboot flash recovery twrp_file_you_downloaded.img (obviously replace with the actual filename)
You can find complete instructions here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
P.S. If the download link for TWRP in the original post does not work, look near the end of the thread. Someone else re-uploaded it.
3.
Its entirely possible that something went afoul during your flashing process. I doubt the guide is to blame, because nearly everyone reported success. Sometimes things just go wrong...?
Good Luck.

samwathegreat said:
1.)
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
Download the correct file for your carrier and try to flash with RSD lite.
You can find a great guide here: http://forum.xda-developers.com/moto...using-t2446515
PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Basically, an SBF is a complete STOCK image of the original filesystem (all partitions). By SBFing, you will be 100% back to factory stock. This method (SBFing) will actually fix a corrupted filesystem.
A "factory reset" does NOT do this. I highly suggest you do the SBF back to stock, and not try just reseting. If there is corruption, reset won't fix it.
2.
Yes! You'll flash TWRP from the "AP Fastboot" screen (bootloader). You must have "mfastboot" downloaded. You'll type:
mfastboot flash recovery twrp_file_you_downloaded.img (obviously replace with the actual filename)
You can find complete instructions here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
P.S. If the download link for TWRP in the original post does not work, look near the end of the thread. Someone else re-uploaded it.
3.
Its entirely possible that something went afoul during your flashing process. I doubt the guide is to blame, because nearly everyone reported success. Sometimes things just go wrong...?
Good Luck.
Click to expand...
Click to collapse
On step 1. It is republic wireless 4.4.2 that I should download right. Correct me if I'm wrong.
Also is there RSDlite for mac or similar software? I tried to google it and xda'd it but I don't think there is. Or any other way to flash it into it.

androiddoglover6969 said:
On step 1. It is republic wireless 4.4.2 that I should download right. Correct me if I'm wrong.
Also is there RSDlite for mac or similar software? I tried to google it and xda'd it but I don't think there is. Or any other way to flash it into it.
Click to expand...
Click to collapse
If you have already received your code, yes, you should flash republic 4.4.2
If you haven't...just wait until you have it for sure. Once you flash 4.4.2 theres no going back. As long as you get unlock code, this is no problem....you'll be able to root regardless.
But, if for any reason he doesn't have your code (unlikely), you'll never be able to root once on 4.4.2....
As of right now (If I understand you completely), since you followed the safestrap guide, you SHOULD be on the jellybean bootloader, so the steps would be different if you didn't have an unlock code (and wanted to retain root).
Don't worry about any of this until we know for sure if you can get unlocked. In the unlikely event you don't get a code, post back here and I will step you through it.
Otherwise (if you get code), yes, start by using RSD Lite to flash the Republic Wireless 4.4.2 SFB per my previous instructions.
EDIT:
Just read the part about being on a MAC. AFAIK, there is no RSD Lite for Mac. We will have to go another route, unless you want to install windows inside a virtual machine....The dev that created the Mac Tooklit sold his X, and its no longer supported.
We will just do manual flashing...make sure you downloaded the "mfastboot" and followed all instructions on the RSD Lite thread I linked, EXCEPT follow the "Manual Flashing" instructions instead.
Extract the Republic Wireless SBF zip file Put the contents in to the same folder where fastboot and mfastboot are located. Here are the commands you will type after booting your X Into bootloader (Fastboot mode):
***Notice that mfastboot is used to flash the system.img. DONT try to use regular fastboot. Just type these commands one at a time.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier sprint ***be sure to type sprint. RW is a sprint MVNO, and I checked the xml file and this is the correct command for the Republic Wireless rom.
fastboot oem fb_mode_clear
Now reboot. Expect it to take a little longer than normal for the first boot-up. Congrats! You're now on 4.4.2 and your corruption issue will be a thing of the past.
Now Complete steps 2 & 3

samwathegreat said:
If you have already received your code, yes, you should flash republic 4.4.2
If you haven't...just wait until you have it for sure. Once you flash 4.4.2 theres no going back. As long as you get unlock code, this is no problem....you'll be able to root regardless.
But, if for any reason he doesn't have your code (unlikely), you'll never be able to root once on 4.4.2....
As of right now (If I understand you completely), since you followed the safestrap guide, you SHOULD be on the jellybean bootloader, so the steps would be different if you didn't have an unlock code (and wanted to retain root).
Don't worry about any of this until we know for sure if you can get unlocked. In the unlikely event you don't get a code, post back here and I will step you through it.
Otherwise (if you get code), yes, start by using RSD Lite to flash the Republic Wireless 4.4.2 SFB per my previous instructions.
EDIT:
Just read the part about being on a MAC. AFAIK, there is no RSD Lite for Mac. We will have to go another route, unless you want to install windows inside a virtual machine....The dev that created the Mac Tooklit sold his X, and its no longer supported.
We will just do manual flashing...make sure you downloaded the "mfastboot" and followed all instructions on the RSD Lite thread I linked, EXCEPT follow the "Manual Flashing" instructions instead.
Extract the Republic Wireless SBF zip file Put the contents in to the same folder where fastboot and mfastboot are located. Here are the commands you will type after booting your X Into bootloader (Fastboot mode):
***Notice that mfastboot is used to flash the system.img. DONT try to use regular fastboot. Just type these commands one at a time.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier sprint ***be sure to type sprint. RW is a sprint MVNO, and I checked the xml file and this is the correct command for the Republic Wireless rom.
fastboot oem fb_mode_clear
Now reboot. Expect it to take a little longer than normal for the first boot-up. Congrats! You're now on 4.4.2 and your corruption issue will be a thing of the past.
Now Complete steps 2 & 3
Click to expand...
Click to collapse
So what you showed me on manual way was if I was to install virtual windows right? Also that link showed it was 4.4 not 4.4.2... so am I still good or I shouldn't do that method? Thanks again for your effort.

androiddoglover6969 said:
So what you showed me on manual way was if I was to install virtual windows right? Also that link showed it was 4.4 not 4.4.2... so am I still good or I shouldn't do that method? Thanks again for your effort.
Click to expand...
Click to collapse
No. What I showed you was the manual fastboot method. This will run on Mac natively. You'll have to download the android SDK for mac, and install, then download the mfastboot binary (either 32 or 64 bit) here: https://gist.github.com/crazed/7670423 *** after you download the file (moto-fastboot-osx64), RENAME it to mfastboot.
Although the link on how to SBF back to stock shows android 4.4, it doesn't matter. The SBF process is the same no matter which version you are on. You just need to download the right carrier/version from here http://sbf.droid-developers.org/phone.php?device=0
Not to confuse you but if you were to install virtual windows, you could probably use the rsd lite method.
Do one but not both. The native (manual) version should be simpler for you. I had assumed you already had the necessary android SDK since you said you went through the whole safestrap process and everything. Were you on a different computer when you did that?
Have you received your code yet? Hold off on SBFing until you have it in hand.

samwathegreat said:
No. What I showed you was the manual fastboot method. This will run on Mac natively. You'll have to download the android SDK for mac, and install, then download the mfastboot binary (either 32 or 64 bit) here: https://gist.github.com/crazed/7670423 *** after you download the file (moto-fastboot-osx64), RENAME it to mfastboot.
Although the link on how to SBF back to stock shows android 4.4, it doesn't matter. The SBF process is the same no matter which version you are on. You just need to download the right carrier/version from here http://sbf.droid-developers.org/phone.php?device=0
Not to confuse you but if you were to install virtual windows, you could probably use the rsd lite method.
Do one but not both. The native (manual) version should be simpler for you. I had assumed you already had the necessary android SDK since you said you went through the whole safestrap process and everything. Were you on a different computer when you did that?
Have you received your code yet? Hold off on SBFing until you have it in hand.
Click to expand...
Click to collapse
Havn't got the code yet. And I did the motowpnomo on windows 8. Everything else did on mac.
Just got my code at 23hrs.
I just wanted to do add onto the process and make minor adjustments to make it clear.
Did Step 1.
and then at the end
He will say reboot, but don't go waiting to install your apps or update it or setting it up. Just start it up normal power up. Then when it says select language (not sure if needs debugging or not but I did) go to developer options by clicking on settings. go all the way down to "about phone" tap on "build number" a couple times you will see developer options pop up. Go back and go down to developer options and go find usb debugging. Then hit accept on phone pop up when usb debugging is enabled so your phone trust your computer. then do ./adb reboot bootloader
It should get you into ap fastboot mode then do my step 2.
Step 2 - Unlock bootloader before doing mfastboot-ing the twrp so you don't get the
invalid image size on your phone
or
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure) on your terminal
So by doing this to unlock bootloader
fastboot getvar all
then
fastboot oem unlock CODEHERE
Should give you a "unlock" blue text with black screen.
Then the step 2 mentioned by samwathegreat for TWRP which will download the file without the invalidity error message on both computer or moto x on ap fastboot screen.
Then step 3. I used the Down arrow to select "recovery" which gave me the TWRP screen.
Step 4. I went into the TWRP screen and hit reboot and a pop up for SuperSU popped up notifying me to install SuperSU. Swipe next and it'll install and then voila!
Step 5. Click on SuperSu app and it should reboot and try to install.
Step 6. Hit the thanks button to samwathegreat

androiddoglover6969 said:
Havn't got the code yet. And I did the motowpnomo on windows 8. Everything else did on mac.
Just got my code at 23hrs.
I just wanted to do add onto the process and make minor adjustments to make it clear.
Did Step 1.
and then at the end
He will say reboot, but don't go waiting to install your apps or update it or setting it up. Just start it up normal power up. Then when it says select language (not sure if needs debugging or not but I did) go to developer options by clicking on settings. go all the way down to "about phone" tap on "build number" a couple times you will see developer options pop up. Go back and go down to developer options and go find usb debugging. Then hit accept on phone pop up when usb debugging is enabled so your phone trust your computer. then do ./adb reboot bootloader
It should get you into ap fastboot mode then do my step 2.
Step 2 - Unlock bootloader before doing mfastboot-ing the twrp so you don't get the
invalid image size on your phone
or
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure) on your terminal
So by doing this to unlock bootloader
fastboot getvar all
then
fastboot oem unlock CODEHERE
Should give you a "unlock" blue text with black screen.
Then the step 2 mentioned by samwathegreat for TWRP which will download the file without the invalidity error message on both computer or moto x on ap fastboot screen.
Then step 3. I used the Down arrow to select "recovery" which gave me the TWRP screen.
Step 4. I went into the TWRP screen and hit reboot and a pop up for SuperSU popped up notifying me to install SuperSU. Swipe next and it'll install and then voila!
Step 5. Click on SuperSu app and it should reboot and try to install.
Step 6. Hit the thanks button to samwathegreat
Click to expand...
Click to collapse
Excellent! Thanks for pointing that the instructions didn't specify that you must unlock your BL before flashing TWRP. Edited Post # 8 to include the step. You can also unlock BL before you start any of the steps, but must do it before flashing custom recovery as you have pointed out.
I did suggest a slightly different method, however, that doesn't require enabling developer options or usb debugging. If you unplug the phone and power it off, you can get straight into fastboot mode without 'adb reboot bootloader'. You just hold down VOL DOWN, and power it on. Then you plug the USB cord back in. It only works if you unplug the phone first....for some reason if you leave it plugged in, you can't power off the phone...it just immediately reboots.
So, to wrap this all up, just a couple more questions:
Did you complete the entire process on your Mac? And can you confirm that the error you were originally receiving (in Original Post) is no longer popping up?
And finally, check out xposed framework installer and "gravity box" mod. You can do some really cool mods with gravity box. I suggest you boot into TWRP and make a nandroid backup -just in case- before you go playing around with xposed.
Have fun.

samwathegreat said:
Excellent! Thanks for pointing that the instructions didn't specify that you must unlock your BL before flashing TWRP. Edited Post # 8 to include the step. You can also unlock BL before you start any of the steps, but must do it before flashing custom recovery as you have pointed out.
I did suggest a slightly different method, however, that doesn't require enabling developer options or usb debugging. If you unplug the phone and power it off, you can get straight into fastboot mode without 'adb reboot bootloader'. You just hold down VOL DOWN, and power it on. Then you plug the USB cord back in. It only works if you unplug the phone first....for some reason if you leave it plugged in, you can't power off the phone...it just immediately reboots.
So, to wrap this all up, just a couple more questions:
Did you complete the entire process on your Mac? And can you confirm that the error you were originally receiving (in Original Post) is no longer popping up?
And finally, check out xposed framework installer and "gravity box" mod. You can do some really cool mods with gravity box. I suggest you boot into TWRP and make a nandroid backup -just in case- before you go playing around with xposed.
Have fun.
Click to expand...
Click to collapse
Yes I complete the whole process on the Mac. Yes the original error is no longer popping up. What is a nandroid back up? I did a back up after I installed all my apps and updated it and dragged that copy to my desktop and uploaded it to my cloud.
I hear about xposed framework and gravity box but I have no clue what it looks like and also forgot what nandroid is but I'll look it up.
And yes android reboots can't stay on shut down when cord is connected. Which is funny.

androiddoglover6969 said:
Yes I complete the whole process on the Mac. Yes the original error is no longer popping up. What is a nandroid back up? I did a back up after I installed all my apps and updated it and dragged that copy to my desktop and uploaded it to my cloud.
I hear about xposed framework and gravity box but I have no clue what it looks like and also forgot what nandroid is but I'll look it up.
And yes android reboots can't stay on shut down when cord is connected. Which is funny.
Click to expand...
Click to collapse
If you backed up from within custom recovery (TWRP), thats the same thing. Some recoveries call them ''backup', some 'nandroid'....same thing.
Thanks for the final follow-up. Take care...

samwathegreat said:
If you backed up from within custom recovery (TWRP), thats the same thing. Some recoveries call them ''backup', some 'nandroid'....same thing.
Thanks for the final follow-up. Take care...
Click to expand...
Click to collapse
Also I installed everything I needed to from gravitybox and well framework xposed too. Which is very similar to jailbreak tweaks on the iPhone.
Thanks again.

Help! OTA - Rebooting

I got a message on my XT1053 Dev that there's a system update. (I'm running stock) I let it download, and then it wanted to reboot. Ok, but it came up in TWRP. I tried rebooting from TWRP every way, but it would not go into maintenance so it could flash the new firmware.
Now whenever I boot it normally, it comes up, and then immediately shuts down, I guess because it wants to upgrade.
What is wrong with this thing?

Quantumstate said:
I got a message on my XT1053 Dev that there's a system update. (I'm running stock) I let it download, and then it wanted to reboot. Ok, but it came up in TWRP. I tried rebooting from TWRP every way, but it would not go into maintenance so it could flash the new firmware.
Now whenever I boot it normally, it comes up, and then immediately shuts down, I guess because it wants to upgrade.
What is wrong with this thing?
Click to expand...
Click to collapse
You must be on stock recovery in order to OTA update. Try going into adb and flashing back to stock recovery and it should work.
Make sure you have mfastboot set up and working, if you need the file respond to this post and I can supply it for you.
Download the stock recovery from here (and make sure it's in your "android" folder)
Boot your phone into fastboot with
adb reboot bootloader
Click to expand...
Click to collapse
-OR-
While the phone is off, hold the PWR button and the Volume Down buttons at the same time for ~5 seconds. Release the PWR button ONLY and continue holding Volume Down until you see the fastboot screen.
Next
Then in adb on your computer perform:
mfastboot flash recovery *filename*
mfastboot reboot
Click to expand...
Click to collapse
When it reboots into the OS it should try to install the update again, like you said it was doing. When it reboots it should update correctly via stock recovery.
Emphasis on should. I can't guaruntee this will work but this is based on my prior knowledge and experience. Good luck and report back with success/problems!

Quantumstate said:
I got a message on my XT1053 Dev that there's a system update. (I'm running stock) I let it download, and then it wanted to reboot. Ok, but it came up in TWRP. I tried rebooting from TWRP every way, but it would not go into maintenance so it could flash the new firmware.
Now whenever I boot it normally, it comes up, and then immediately shuts down, I guess because it wants to upgrade.
What is wrong with this thing?
Click to expand...
Click to collapse
There's nothing wrong with this thing....
All of the guides here exist for a reason. One responsibility you have once you have decided to root your device or install custom recovery, is that when a new OTA comes out, you must check back here at XDA to see what the procedure for installing it is.
All of the guides here tell you that you MUST have stock recovery in order to accept any updates.
Here's how you will fix it:
Boot into TWRP. Clear your cache. This will prevent the constant reboots.
Now, use fastboot to flash back the stock recovery. You will need to download the 4.4.2 SBF for your XT1053 from here: http://sbf.droid-developers.org/phone.php?device=0
Extract the archive. You only need one file: recovery.img
You should already have the android SDK installed since you unlocked your BL and flashed TWRP. Use fastboot to flash the stock recovery:
fastboot flash recovery recovery.img
Now you can accept the OTA from your phone. You may need to go to Settings > About Phone > System Updates and re-download it.
The OTA should now successfully install (assuming you aren't using Xposed or made any other modifications).
Now, you can flash TWRP recovery back. Let us know how it works out for you...

Thanks, but the update was unsuccessful.
I seem to remember that the update checks existing files, and if one has the wrong CRC it fails. Well I'm stock but rooted. It is a develoepr's phone and there is no developer's image on those sites.

Quantumstate said:
Thanks, but the update was unsuccessful.
I seem to remember that the update checks existing files, and if one has the wrong CRC it fails. Well I'm stock but rooted. It is a develoepr's phone and there is no developer's image on those sites.
Click to expand...
Click to collapse
The GSM Developer edition uses the SAME exact software as the T-Mobile version. The T-Mobile variant has zero bloat, and no carrier branding. The only difference between the two is that you don't lose your warranty when you unlock the GSM Dev edition.
You're looking for the XT1053 T-Mobile SBF
http://sbf.droid-developers.org/phone.php?device=0

Quantumstate said:
Thanks, but the update was unsuccessful.
I seem to remember that the update checks existing files, and if one has the wrong CRC it fails. Well I'm stock but rooted. It is a develoepr's phone and there is no developer's image on those sites.
Click to expand...
Click to collapse
I always seem to have something in /system that messes with the ota update. In addition to flashing stock recovery to replace twrp, I also flash system.img (with mfastboot only) from the same sbf as you get the recovery.img. Then the ota goes through without a hitch.

Still Errors at the robot with spinning diamond heart, even with TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml/recovery.img.
Looking around it seems that here are some rules. I think I'm violating #2: "Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall." I've removed most of the G**gle junk since I don't trust them.
So if this is what they require, Hell with them. If it were possible to put multiboot on the Moto X I would have done it a long time ago. Maybe I can apply this OTA update in some other way? Without going through their rinky-dink tests?

Quantumstate said:
Still Errors at the robot with spinning diamond heart, even with TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml/recovery.img.
Looking around it seems that here are some rules. I think I'm violating #2: "Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall." I've removed most of the G**gle junk since I don't trust them.
So if this is what they require, Hell with them. If it were possible to put multiboot on the Moto X I would have done it a long time ago. Maybe I can apply this OTA update in some other way? Without going through their rinky-dink tests?
Click to expand...
Click to collapse
You are correct on the manifest.
Instead, just flash the entire stock SBF (TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25). The manual method is easiest.
Or you could just flash the system.img as the earlier poster suggested.
This will revert to stock, and you will have to reinstall your apps, but the OTA WILL work afterwards. You really should consider just 'freezing' the google apps instead of removing them this time...
The only other way you will be able to install the OTA is to put all the gapps back on...but I doubt you made a backup, right?
mfastboot flash system system.img
that should be all you need (beside stock recovery, of course). Then take the update, and finally do whatever mods you want remembering that you will HAVE to un-do the mods to be able to accept future OTAs without returning to 100% stock again.
Good Luck

Flashing system.img will not require you to reinstall your downloaded apps, just apps you installed as system apps via root access. Downloaded apps are in the /data/app partition that is not affected by a system.img flash.

I finally went this route. I'm not putting up with their OTA requirements; I'll get the upgrade without them. Although, that 4.3 sure has alot of G**gle and Motorola bloatware to remove.
With Xposed, GravityBox (and other modules) I now have the flexibility I was looking for.
Now all I need is a better dialer than the crappy G**gle one, and secure SMS.