I am trying to root my att moto x (to be honest I am not a developer, so I just followed the guide 'Rockmymoto') then when I am trying to use Cydia Impactor to telnet my phone, it shows 'install parse failed no certificates'. I am using a Windows8.1 laptop, I've also got a Mac, but it seems not the computers' problem, what should I do now.
The only reason I want to root my phone is becasue I want to give it to my father, however it keeps noticing me the 4.4.3OTA, it is so annoying and I cannot turn it off. I heard that the only way to stop it is to root my phone and delet the OTA application. Please help me with it, thank you.
By the way, I am using the latest cydia impactor.
Sean-xb said:
I am trying to root my att moto x (to be honest I am not a developer, so I just followed the guide 'Rockmymoto') then when I am trying to use Cydia Impactor to telnet my phone, it shows 'install parse failed no certificates'. I am using a Windows8.1 laptop, I've also got a Mac, but it seems not the computers' problem, what should I do now.
The only reason I want to root my phone is becasue I want to give it to my father, however it keeps noticing me the 4.4.3OTA, it is so annoying and I cannot turn it off. I heard that the only way to stop it is to root my phone and delet the OTA application. Please help me with it, thank you.
By the way, I am using the latest cydia impactor.
Click to expand...
Click to collapse
RockMyMoto is for Jelly Bean 4.2.2_12.15.15 only..not KK
Also..not to delete the OTA..BUT..Freeze with Titanium Backup Pro, the MotorolaOTA 1.0
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
RockMyMoto is for Jelly Bean 4.2.2_12.15.15 only..not KK
Also..not to delete the OTA..BUT..Freeze with Titanium Backup Pro, the MotorolaOTA 1.0
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Click to expand...
Click to collapse
He'd need root for titanium backup.
And to the original poster......do not try to downgrade if you're on 4.4.2 now. You will likely brick, if not now....later. Just don't try it.
Sean-xb said:
I am trying to root my att moto x (to be honest I am not a developer, so I just followed the guide 'Rockmymoto') then when I am trying to use Cydia Impactor to telnet my phone, it shows 'install parse failed no certificates'. I am using a Windows8.1 laptop, I've also got a Mac, but it seems not the computers' problem, what should I do now.
The only reason I want to root my phone is becasue I want to give it to my father, however it keeps noticing me the 4.4.3OTA, it is so annoying and I cannot turn it off. I heard that the only way to stop it is to root my phone and delet the OTA application. Please help me with it, thank you.
By the way, I am using the latest cydia impactor.
Click to expand...
Click to collapse
Your post doesn't really make sense....
You say you are using an AT&T Moto X, right? Then later you say that it keeps prompting you to install the "4.4.3" update?
AT&T never released a 4.4.3 update. The latest software version for the AT&T XT1058 is 4.4.2.
So which version are you CURRENTLY on? And what is the model of your phone? Go to Settings > About Phone > Status
The ONLY way you can use RockMyMoto is if you are currently on 4.4 or 4.2.2.
Let us know which version you are actually on, and we MAY be able to help you further.
Also, if the only reason you want to root is to disable firmware updates........why? Why not just accept the update, and then it will stop nagging you?
It sounds to me like you might have the "GSM Unlocked" version....the XT1053, and you just happen to be using it on AT&T. Please clarify.
Sorry for the incorrect information, but it is an AT&T Moto X. There is no 'simplified Chinese' in the original rom, so I swipe in a Rogers' rom which comes with the language. And then it means that it cannot accept any OTA or it will become a brick. It keeps notifying me the 4.4.3 OTA which is really annoying. And I need to root first before I can freeze that OTA app. here comes the pictures
samwathegreat said:
Your post doesn't really make sense....
You say you are using an AT&T Moto X, right? Then later you say that it keeps prompting you to install the "4.4.3" update?
AT&T never released a 4.4.3 update. The latest software version for the AT&T XT1058 is 4.4.2.
So which version are you CURRENTLY on? And what is the model of your phone? Go to Settings > About Phone > Status
The ONLY way you can use RockMyMoto is if you are currently on 4.4 or 4.2.2.
Let us know which version you are actually on, and we MAY be able to help you further.
Also, if the only reason you want to root is to disable firmware updates........why? Why not just accept the update, and then it will stop nagging you?
It sounds to me like you might have the "GSM Unlocked" version....the XT1053, and you just happen to be using it on AT&T. Please clarify.
Click to expand...
Click to collapse
Related
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Icon000 said:
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Click to expand...
Click to collapse
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
matt99017d said:
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
Icon000 said:
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
Click to expand...
Click to collapse
the only rom out for SS that i am aware of is just a ported tmobile rom for vzw phones that has the update built in. Basically it is just the OTA stock rom running on SS. This is what I am using currently. Not sure if it flashable for ATT phones, but I'm sure there is some workaround there. Or maybe the OP on that thread can make a ATT one if you asked him. SS is stable as of now. Haven't had any new updates to it because no one is having any problems currently (at least with moto x devices).
For your question pertaining to options for taking the OTA. There are 4 methods now.
1. SS method described above
2. use the thread called something like "keep root through the OTA." It basically takes the ota without updating the BL so you can still downgrade to your stock original FW that you are on now. It's the same thing as the SS method because SS also does not udpate the BL, but you won't be using SS for this method obviously.
3. you can flash recovery.img (and system.img if you need to) or just RSD, then install pwnmymoto without running it, then take the ota and pwnmymoto will root the phone automatically after the ota is taken. you won't be able to downgrade your FW anymore with this method.
4. you can just take the ota (also must flash or use rsd to take it obviously) and then use jcase's rockmymoto root exploit. This uses adb commands and telnet stuff. Not too difficult but if you are unfamiliar with all of that then it will take at least some reading. There is also a thread out there for windows users that simplifies it pretty well.
For future Kit kat root. it is still up in the air what will happen with that. I chose to use SS because it was easy. quick. and allows me to make nandroids. I also like knowing that I can still flash to original stock FW in case that might be necessarry for getting root on kit kat. This seems less likely now that jcase created a root method for the OTA that is out, but I'm still just playing it safe personally, even if it might be pointless now.
I recently rooted my Verizon G2 with ioroot, Android version is currently 4.2.2. Now Verizon keeps pushing to update to 4.4.2, and reminds me every 12 hours to do so. The update fails, and I'm assuming because the phone is rooted. So I guess a couple questions:
(1) Is there a way to prevent it from asking for an update, and I'll just stick with 4.2.2?
(2) How do I "unroot" my phone? Is there a simple way to reverse the process, and also how do I root it when I get to 4.4.2?
Thanks!
EDIT: I saw this guide, just the title didn't sound like it was related to root, but at least I can try this: http://forum.xda-developers.com/showthread.php?t=2729156
But I'd still like to see if there's a way to stay with 4.2.2 instead, do I really need 4.4.2?
HTWingNut said:
I recently rooted my Verizon G2 with ioroot, Android version is currently 4.2.2. Now Verizon keeps pushing to update to 4.4.2, and reminds me every 12 hours to do so. The update fails, and I'm assuming because the phone is rooted. So I guess a couple questions:
(1) Is there a way to prevent it from asking for an update, and I'll just stick with 4.2.2?
(2) How do I "unroot" my phone? Is there a simple way to reverse the process, and also how do I root it when I get to 4.4.2?
Thanks!
EDIT: I saw this guide, just the title didn't sound like it was related to root, but at least I can try this: http://forum.xda-developers.com/showthread.php?t=2729156
But I'd still like to see if there's a way to stay with 4.2.2 instead, do I really need 4.4.2?
Click to expand...
Click to collapse
You can use TitaniumBackup and freeze the OTA updater apk. I don't know the exact apk name so hopefully someone can chime in. Also you can do a full unroot by going into the SuperUser app and clicking on Full Unroot. It will do it's thing and you will reboot.
EDIT: I forgot to mention that root does NOT kill the OTA. You most likely have a custom recovery on your phone. That's why it fails. So all you have to do is just freeze the annoying updater apk and you should be good to go.
Thanks! I'll see if I can find the ota updater apk and freeze it.
Beamed from my G2 Tricorder
You could always just flash one of the 4.4.2 stock LG ROMs like Malladus or xdabbebs. If you have a custom recovery that is.
HTWingNut said:
Thanks! I'll see if I can find the ota updater apk and freeze it.
Beamed from my G2 Tricorder
Click to expand...
Click to collapse
Please let us know if you find it...I am in the same boat and I cannot find what to freeze either.
System updates MUC 6.4.1.5_E02
Sent from my VS980 4G using Tapatalk
---------- Post added at 04:14 PM ---------- Previous post was at 04:10 PM ----------
At least in xdabbeb's ROM
Sent from my VS980 4G using Tapatalk
Ok, I think I figured it out. MUC 6.4.1.5_E02 was disabled by default when I upgraded to Titanium Backup Pro.
I'm on Verizon 4.4 never took update since no root (that I know of) woke up a few days ago and saw titanium backup said "unable to gain root access" somehow I lost it? I used jcades way with adb and gained root.. Killed WP. I downloaded root checker and said I had none.. Ideas?
Slapped my Moto
I don't know how root would go away without something on your phone changing...but best place to ask might be in the thread you got the root method from.
xpsychox said:
I'm on Verizon 4.4 never took update since no root (that I know of) woke up a few days ago and saw titanium backup said "unable to gain root access" somehow I lost it? I used jcades way with adb and gained root.. Killed WP. I downloaded root checker and said I had none.. Ideas?
Slapped my Moto
Click to expand...
Click to collapse
Sounds like you either accepted the OTA to 4.4.2, or the 4.4.2 OTA was FORCED on you. Double check your phone under Settings -> About.
With 4.4.2, the vulnerability that allowed MotoWpNoMo to disable write protection with a locked bootloader has been patched, and the ability to safely and successfully downgrade your ROM to 4.4 and below (in order to make use of MotoWpNoMo to disable write protection, and SlapyMyMoto or the like to root) has been taken away too. No new vulnerabilities have been found, nor has a replacement for MotoWpNoMo been found/created/released.
In short, if you have 4.4.2 or above on your X, and you can't unlock the booloader (like Verizon and ATT, unless you are able to make use of the Chinese web site or MiddleMan), you can't disable write protection (so any apps that need to write/save to /system, /system/bin, etc wont work even if you manage to gain root) and while PIE roots 4.4.2 it is "temporary" in that its lost every time you reboot (power off/on). NOTE: the vulnerability used is patched in 4.4.3 so PIE can't be used on 4.4.3 and above.
If by chance you are still on 4.4,I don't know why you would have lost root, but I would consider backing everything up,flashing the stock VZW 4.4 SBF, and following the SlapMyMoto/MotoWpNoMo processes from scratch. When completed find the /System/priv-app/3C_OTA.APK and rename it so your phone doesn't check for future OTA's.
I've got moto ota froze..
Slapped my Moto
xpsychox said:
I've got moto ota froze..
Slapped my Moto
Click to expand...
Click to collapse
And did you double check your version?
Yes..checked before postinf
Slapped my Moto
Screen shot that I just took
Slapped my Moto
xpsychox said:
Screen shot that I just took
Slapped my Moto
Click to expand...
Click to collapse
And you never flashed 4.4.2 and downgraded to 4.4, right?
Yes..I used the jcase method by adb shell before someone made a tool.. With slapmymoto etc.like in said wokebup one day (about a week ago?) And said no more root?
Slapped my Moto
xpsychox said:
Yes..I used the jcase method by adb shell before someone made a tool.. With slapmymoto etc.like in said wokebup one day (about a week ago?) And said no more root?
Slapped my Moto
Click to expand...
Click to collapse
I have no idea then. The only times I've seen root lost is those where update was forced on them. And the only time I've seen root lost when using SlapMyMoto/MotoWPNoMO on reboot was one or two who had 4.4.2 and did a partial down grade to 4.4 and tried Slap/WpNoMo.
When I get home I'll have to try and re root...
Slapped my Moto
I just noticed something strange as I was checking my root and updates status, system updates is now at the bottom of the menu .. used to be top. I rooted with slap and than renamed the 3c_ota.apk and .odex files and I force a system update check and it fails.. so im still good on root but dont know how the menu has changed on my phone. I dont freeze anything dont have titanium thing installed..
This is weird...lol
Slapped my Moto
so i've decided to go ahead and try to re root my moto x. I'm following the instructions i did last time, the slapmymoto (don't need to do motowpnomo cuz i did check the WP, i have 0), pushed rockmymoto but i can't get cydia impactor to connect, keeps saying "signature bugs unavailable" and if i click "usb" drop down and say "scan for device" it say "no device" ideas?
xpsychox said:
so i've decided to go ahead and try to re root my moto x. I'm following the instructions i did last time, the slapmymoto (don't need to do motowpnomo cuz i did check the WP, i have 0), pushed rockmymoto but i can't get cydia impactor to connect, keeps saying "signature bugs unavailable" and if i click "usb" drop down and say "scan for device" it say "no device" ideas?
Click to expand...
Click to collapse
Straight from jcase's slapmymoto thread: "This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4."
Your screenshot shows that you are running 4.4. Additionally, you start off saying you followed instructions for slapmymoto, then you reference rockmymoto... Which one are you using? Or are you using both?
Additionally, you need to be VERY careful if you downgrade. Follow jcase's instructions exactly. There is a big risk of bricking if you make even one innocent mistake.
Please advise...
samwathegreat said:
Straight from jcase's slapmymoto thread: "This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4."
Your screenshot shows that you are running 4.4. Additionally, you start off saying you followed instructions for slapmymoto, then you reference rockmymoto... Which one are you using? Or are you using both?
Additionally, you need to be VERY careful if you downgrade. Follow jcase's instructions exactly. There is a big risk of bricking if you make even one innocent mistake.
Please advise...
Click to expand...
Click to collapse
I was pushing both BC it says to..as I said in first post I did jcases root and had then somehow lost it... So idk how/why just did.. I was hoping I didn't have to downgrade but I had a feeling... But even so it wouldn't explain why I can't use the err.. That program that starts with a c.. Only thing I can remember from last time I think I had to play with my phone setting and put it from USB to photo mode or something like that... Other thing I have thought about is now I am using a cradle point mbr95 modem/router combo. Idk if it blocks it? I know HW to downgrade to 4.2.2 u have to edit one of the lines in the script for the fxz. Done it before... Just don't understand why that program wouldn't work?
Slapped my Moto
Have you tried going into SuperSU > settings tab > unchecking and checking "enable superuser"? I know this sounds like a stupid question but sometimes stating the obvious can help narrow things down. I had this problem on my old Skyrocket before where I would suddenly lose root but be able to gain it back again simply by refreshing this setting in SuperSU.
1ad_m12 said:
Have you tried going into SuperSU > settings tab > unchecking and checking "enable superuser"? I know this sounds like a stupid question but sometimes stating the obvious can help narrow things down. I had this problem on my old Skyrocket before where I would suddenly lose root but be able to gain it back again simply by refreshing this setting in SuperSU.
Click to expand...
Click to collapse
Wtf.... Wow disabled and renamed and it worked.... Never heard if it.. Thanks!!
Slapped my Moto
xpsychox said:
Wtf.... Wow disabled and renamed and it worked.... Never heard if it.. Thanks!!
Slapped my Moto
Click to expand...
Click to collapse
:good: glad to help!
1ad_m12 said:
:good: glad to help!
Click to expand...
Click to collapse
I still can't believe that worked... Lol
Slapped my Moto
Hi. Sorry to bother - didnt find an answere. I have Moto X from ATT ( Android 4.2.2). It was rooted by seller - so I recieved it as it is. Now I want to install 4.4, but at first I need it back to factory. I've tried to wipe it from menu - nothing. Its reboot and nothing happends. Ive tried to do it from recovery - it's just rebooting and its it. Help please
Vebr137 said:
Hi. Sorry to bother - didnt find an answere. I have Moto X from ATT ( Android 4.2.2). It was rooted by seller - so I recieved it as it is. Now I want to install 4.4, but at first I need it back to factory. I've tried to wipe it from menu - nothing. Its reboot and nothing happends. Ive tried to do it from recovery - it's just rebooting and its it. Help please
Click to expand...
Click to collapse
Have you tried using RSDLite to flash the original ROM?
Vebr137 said:
Hi. Sorry to bother - didnt find an answere. I have Moto X from ATT ( Android 4.2.2). It was rooted by seller - so I recieved it as it is. Now I want to install 4.4, but at first I need it back to factory. I've tried to wipe it from menu - nothing. Its reboot and nothing happends. Ive tried to do it from recovery - it's just rebooting and its it. Help please
Click to expand...
Click to collapse
It has probably been rooted using an exploit. Be VERY careful or you could lose root forever.
Is the bootloader unlocked? Let me know and I may be able to help you with clear and precise steps.
Vebr137 said:
Hi. Sorry to bother - didnt find an answere. I have Moto X from ATT ( Android 4.2.2). It was rooted by seller - so I recieved it as it is. Now I want to install 4.4, but at first I need it back to factory. I've tried to wipe it from menu - nothing. Its reboot and nothing happends. Ive tried to do it from recovery - it's just rebooting and its it. Help please
Click to expand...
Click to collapse
If you erase..are you aware that you will loose Root permanently.?
BUT..If you use the (jcase) RockMyMoto & SlapMyMoto, you can retain Root with these two exploits, Since your device is still on Jelly Bean OS..BUT..to do so, one must be experienced with adb & RSDLite..and you can retain Root over into 4.4_
Sent from my:
Jaocagomez Debloated ROM
4.4.4_21.11.21 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
dier325 said:
Have you tried using RSDLite to flash the original ROM?
Click to expand...
Click to collapse
I did. Its just rebooting and its all.
samwathegreat said:
It has probably been rooted using an exploit. Be VERY careful or you could lose root forever.
Is the bootloader unlocked? Let me know and I may be able to help you with clear and precise steps.
Click to expand...
Click to collapse
Bootloader is locked. Thanks)
NWKENT said:
If you erase..are you aware that you will loose Root permanently.?
BUT..If you use the (jcase) RockMyMoto & SlapMyMoto, you can retain Root with these two exploits, Since your device is still on Jelly Bean OS..BUT..to do so, one must be experienced with adb & RSDLite..and you can retain Root over into 4.4_
Sent from my:
Jaocagomez Debloated ROM
4.4.4_21.11.21 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Click to expand...
Click to collapse
Root for this phone is not that important. Im tired that every time I want update a program or install a new one I need to delete google profile from the phone, reboot it and again use google profile. Otherwise nothing is installing.
Vebr137 said:
Root for this phone is not that important. Im tired that every time I want update a program or install a new one I need to delete google profile from the phone, reboot it and again use google profile. Otherwise nothing is installing.
Click to expand...
Click to collapse
If root isn't important to you......BY FAR, the easiest solution is to follow the instructions in the "Return to Stock" thread - in general subforum, and flash the entire 4.4.2 SBF to your phone. Everything you need is in that thread, including links to drivers, tools, and the SBF files themselves.
Just keep in mind - you'll permanently lose root/wp-off. You can still use the temp-root methods, for now...but once you update to 4.4.4 (it will be pushed out to everyone SOON), you will have ZERO chance at rooting (unless a new exploit comes along, which is extremely unlikely, OR you get your bootloader unlocked through the middleman).
Good Luck!
samwathegreat said:
If root isn't important to you......BY FAR, the easiest solution is to follow the instructions in the "Return to Stock" thread - in general subforum, and flash the entire 4.4.2 SBF to your phone. Everything you need is in that thread, including links to drivers, tools, and the SBF files themselves.
Just keep in mind - you'll permanently lose root/wp-off. You can still use the temp-root methods, for now...but once you update to 4.4.4 (it will be pushed out to everyone SOON), you will have ZERO chance at rooting (unless a new exploit comes along, which is extremely unlikely, OR you get your bootloader unlocked through the middleman).
Good Luck!
Click to expand...
Click to collapse
Thnx)
We have a Moto X from Verizon. We built it with the Moto Maker and got it in December.
At that time, we immediately did whatever secret handshake to get root (something about downgrading). It's been humming along fine for the longest time. At one point, it appears, we took the OTA update and now root is gone. This has been the case for a while, and it hasn't been an issue. Now, the phone is trying to take the Android 4.4.4 upgrade, and the device keeps rebooting and displaying this error:
"Partition (recovery) security version downgraded"
Click to expand...
Click to collapse
We've done some research, and believe I have a path to recover. We don't care about root or custom recovery any longer, we just want a working Moto X.
Question: since I'm on 4.4.2 currently (build KXA20.16-1.25.2), I'm assuming I can use the 4.4.2 FKZ to return to stock?
Here's the thread I used to help me make this determination: http://forum.xda-developers.com/moto-x/general/bricked-attempting-4-4-to-4-4-2-ota-look-t2660441
Can someone validate that I'm going down the right path? Thanks in advance for all replies!
fonixmunkee said:
We have a Moto X from Verizon. We built it with the Moto Maker and got it in December.
At that time, we immediately did whatever secret handshake to get root (something about downgrading). It's been humming along fine for the longest time. At one point, it appears, we took the OTA update and now root is gone. This has been the case for a while, and it hasn't been an issue. Now, the phone is trying to take the Android 4.4.4 upgrade, and the device keeps rebooting and displaying this error:
We've done some research, and believe I have a path to recover. We don't care about root or custom recovery any longer, we just want a working Moto X.
Question: since I'm on 4.4.2 currently (build KXA20.16-1.25.2), I'm assuming I can use the 4.4.2 FKZ to return to stock?
Here's the thread I used to help me make this determination: http://forum.xda-developers.com/moto-x/general/bricked-attempting-4-4-to-4-4-2-ota-look-t2660441
Can someone validate that I'm going down the right path? Thanks in advance for all replies!
Click to expand...
Click to collapse
Use the FXZ that has been posted for your model: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
It is the only safe way to upgrade now that you are receiving the error, which normally indicates that you attempted to downgrade.
If you use one of @SamuriHL 's tools, you can KEEP your data, just like you would if you used took the OTA.
samwathegreat said:
Use the FXZ that has been posted for your model: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
It is the only safe way to upgrade now that you are receiving the error, which normally indicates that you attempted to downgrade.
If you use one of @SamuriHL 's tools, you can KEEP your data, just like you would if you used took the OTA.
Click to expand...
Click to collapse
Thanks for the reply, samwathegreat. After conducting a bit more research, I saw your name pop up a few times assisting people with a similar error.
So if I may ask a follow-on question, should I use the FXZ for 4.4.2, or can I do the 4.4.4 one? I'm currently on 4.4.2, receiving said error, while attempting to upgrade to 4.4.4.
fonixmunkee said:
Thanks for the reply, samwathegreat. After conducting a bit more research, I saw your name pop up a few times assisting people with a similar error.
So if I may ask a follow-on question, should I use the FXZ for 4.4.2, or can I do the 4.4.4 one? I'm currently on 4.4.2, receiving said error, while attempting to upgrade to 4.4.4.
Click to expand...
Click to collapse
You should definitely use the 4.4.4 FXZ from the link I provided you. If you do this, you will be on 4.4.4 running smoothly in no time at all...
Thank you, @samwathegreat! You had the fix:
1. Download the 4.4.4 FXZ from here, even though we were on 4.4.2: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
2. Follow the steps to use RSD flasher from @SamuriHL. Follow them to the T: http://www.droidrzr.com/index.php/topic/48904-rsd-flasher-beta-windows-only/
Our Moto X is now running 4.4.4 stock. Thanks to @samwathegreat & @SamuriHL!