[Q] "Partition (recovery) security version downgraded" XT1060 VZW - Moto X Q&A

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!

Related

[Q] Can I update? Confused by so many unclear posts.

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.

[Q] AT&T - haven't gotten OTA notification still

Okay, so I see all these threads with everyone saying they have the official 4.4 OTA. My mom's AT&T Moto X still hasn't gotten it…is there something wrong with her phone?
If there's not a fix, can I download the official 4.4 OTA and flash it somehow? Her phone is not rooted or unlocked, and I don't intended to do either to the phone.
darnocs1 said:
Okay, so I see all these threads with everyone saying they have the official 4.4 OTA. My mom's AT&T Moto X still hasn't gotten it…is there something wrong with her phone?
If there's not a fix, can I download the official 4.4 OTA and flash it somehow? Her phone is not rooted or unlocked, and I don't intended to do either to the phone.
Click to expand...
Click to collapse
4.4? or 4.4.2?
4.4.2 isn't out for the ATT locked Moto X yet.
Either. I am still on 4.2.2.
Sent from my Galaxy S3 running agriff's i747z ROM (4.1.2)
darnocs1 said:
Either. I am still on 4.2.2.
Click to expand...
Click to collapse
Go here and download the Motorola Device Manager and you can update it through that. It is a lot safer.
Motorola Device Manager
Instructions for Using Motorola Device Manager to Update Your Moto X
If that doesn't work, you are going to need to back up her phone and do a factory reset.
I'm in the same situation
I retruned my moto x to carrier for a replacement(this one had all ota), and the new one doesn't receive any ota so far(1 week since this), nothing worked, Device Manager, Restoring it, Wipe Data/cache, Deleting cache from Framework google o reset the process, switched to 3g wifi,etc. What should i do?
PS: I phoned motorola and claro, they are tossing the ball beetween them
ganasiff said:
I retruned my moto x to carrier for a replacement(this one had all ota), and the new one doesn't receive any ota so far(1 week since this), nothing worked, Device Manager, Restoring it, Wipe Data/cache, Deleting cache from Framework google o reset the process, switched to 3g wifi,etc. What should i do?
PS: I phoned motorola and claro, they are tossing the ball beetween them
Click to expand...
Click to collapse
How did you restore it, factory reset? If so, you could try using RSD Lite to flash the sbf firmware for your carrier. You need the app MotorolaOTA to get the update. Maybe there is a problem with MotorolaOTA. If you froze MotorolaOTA, that is the problem.
If flashing the firmware for your carrier using RSD Lite doesn't work, it sounds like an IMEI problem with Motorola not recognizing your IMEI as being in need of the OTA. Call Motorola back and try to get to Tech Level 3. The first level are not very tech savvy. Next level is better, but not as good as Tech Level 3. You have to wait for a call back to get to Tech Level 3 or at least I did.
Cozume said:
How did you restore it, factory reset? If so, you could try using RSD Lite to flash the sbf firmware for your carrier. You need the app MotorolaOTA to get the update. Maybe there is a problem with MotorolaOTA. If you froze MotorolaOTA, that is the problem.
If flashing the firmware for your carrier using RSD Lite doesn't work, it sounds like an IMEI problem with Motorola not recognizing your IMEI as being in need of the OTA. Call Motorola back and try to get to Tech Level 3. The first level are not very tech savvy. Next level is better, but not as good as Tech Level 3. You have to wait for a call back to get to Tech Level 3 or at least I did.
Click to expand...
Click to collapse
I've done that too, RSDLite flash, i think i'll go for tech level 3 supp, how do i get that? Can i ask straight forward to it?.
Thanks for the reply
ganasiff said:
I've done that too, RSDLite flash, i think i'll go for tech level 3 supp, how do i get that? Can i ask straight forward to it?.
Thanks for the reply
Click to expand...
Click to collapse
You can always ask. I had to go through Tech Level 2 before I got a call back. They are based in Texas so call during M-F 9-5 CST.
darnocs1 said:
Okay, so I see all these threads with everyone saying they have the official 4.4 OTA. My mom's AT&T Moto X still hasn't gotten it…is there something wrong with her phone?
If there's not a fix, can I download the official 4.4 OTA and flash it somehow? Her phone is not rooted or unlocked, and I don't intended to do either to the phone.
Click to expand...
Click to collapse
Yes you can install RSD Lite and then "flash" ATT_XT1058_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml
google the file name, download it and upzip it
---------- Post added at 04:49 AM ---------- Previous post was at 04:45 AM ----------
ganasiff said:
I've done that too, RSDLite flash, i think i'll go for tech level 3 supp, how do i get that? Can i ask straight forward to it?.
Thanks for the reply
Click to expand...
Click to collapse
if rsdlite doesnt work, like when i was trying to downgrade from 4.4 to 4.2.2, try MotoXtoolkit, it worked for me
Figured it out
Cozume said:
How did you restore it, factory reset? If so, you could try using RSD Lite to flash the sbf firmware for your carrier. You need the app MotorolaOTA to get the update. Maybe there is a problem with MotorolaOTA. If you froze MotorolaOTA, that is the problem.
If flashing the firmware for your carrier using RSD Lite doesn't work, it sounds like an IMEI problem with Motorola not recognizing your IMEI as being in need of the OTA. Call Motorola back and try to get to Tech Level 3. The first level are not very tech savvy. Next level is better, but not as good as Tech Level 3. You have to wait for a call back to get to Tech Level 3 or at least I did.
Click to expand...
Click to collapse
Aha! When you said "freeze MotoOTA" that reminded me that I had disabled the app because it kept FCing when I got the phone. I enabled that…we'll see if it works now.

Receiving Moto X DE (GSM) soon, should I stay with JB?

Does new phone come with JB? If so should I stay with it and not to accept OTA?
It seems that Kitkat update introduced several issues (problem with email syncing, bluetooth incompatibility wit some cars, etc). Is there anything else? I am fine with not having the latest and greatest.
Also: is it possible to downgrade Moto X DE (GSM) back to JB? I am not 100% sure from reading this forum.
The kit Kat update had issues but nothing on the scale of the Samsung galaxy family's 4.3 update. I haven't noticed any issue on mine nor any on customers. Totally worth upgrading it.
Sent from my Lumia 928
The only issue I am having with mine is that while it says its connected to web (either lte or wifi) it won't actually connect. A reboot fixes the issue until it comes back.
texanman said:
The only issue I am having with mine is that while it says its connected to web (either lte or wifi) it won't actually connect. A reboot fixes the issue until it comes back.
Click to expand...
Click to collapse
Did you have this issue while on JB?
Dont know as mine came with 4.4 which did not have this weird issue. It may be something I installed so a wipe may be in order.
Go to KK, no question
tapped out via XT1053 DE
The only issue I had was Google maps not showing my direct location with high accuracy on. It was hard for me to distinguish if I needed to go right or left then it has a hard time rerouting. Which pissed my wife off lol.
MOTO X Slapped
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Don't forget text reflow has been deprecated. Major loss in browsers and reading apps.
Sent from my XT1053 using HoFo mobile app.
---------- Post added at 07:45 AM ---------- Previous post was at 07:36 AM ----------
@rbiter said:
Don't forget text reflow has been deprecated. Major loss in browsers and reading apps. Blink is in web view. Also means invert lost.
Sent from my XT1053 using HoFo mobile app.
Click to expand...
Click to collapse
Sent from my XT1053 using HoFo mobile app.
eksasol said:
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Click to expand...
Click to collapse
Mine arrived with 4.2.2 installed, (2 weeks ago) and it took two updates to get to 4.4, 1'st 4.2.2 then 4.4. No regrets on the update for me, but then again I let the updates fly when I turned on the phone.
eksasol said:
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Click to expand...
Click to collapse
Just got my vzw DE wednesday, 2/12/2014. Came with 4.2.2 pre-camera update. soon as it booted it took the 4.2.2 camera update, then shortly after that came 4.4. did all the updates then unlocked the bootloader, installed twrp and rooted. happy as a clam!
Teksu said:
Just got my vzw DE wednesday, 2/12/2014. Came with 4.2.2 pre-camera update. soon as it booted it took the 4.2.2 camera update, then shortly after that came 4.4. did all the updates then unlocked the bootloader, installed twrp and rooted. happy as a clam!
Click to expand...
Click to collapse
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
if you have any other question please post or PM me
dray_jr said:
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
if you have any other question please post or PM me
Click to expand...
Click to collapse
That makes it very clear. But can you elaborate on why downgrade from 4.4.2 is not possible? I currently use rooted Droid Incredible on Verizon with CM 7.1 and if I am not mistaken I can flash pretty much any previous ROM I want (I really haven't tinkered with it for last couple of years, so I may be wrong).
JoeSchmoe007 said:
That makes it very clear. But can you elaborate on why downgrade from 4.4.2 is not possible? I currently use rooted Droid Incredible on Verizon with CM 7.1 and if I am not mistaken I can flash pretty much any previous ROM I want (I really haven't tinkered with it for last couple of years, so I may be wrong).
Click to expand...
Click to collapse
Moto changed the bootloader in 4.4.2 and they dont allow you to downgrade
Moto X DE - mine coming soon as well - some questions
dray_jr said:
Moto changed the bootloader in 4.4.2 and they dont allow you to downgrade
Click to expand...
Click to collapse
My VZW Moto X DE is on its way to me, and I've spent a bunch of time on the forums yet still have the following questions and hope you can help. My current phone is an original Droid Incredible, which I rooted, mostly for recovery, backups, tethering, and system monitoring. This site was a great resource back when I did that and I greatly appreciated the information.
RE: the Moto X, I've read the steps for unlocking the bootloader and which paths for upgrading/downgrading are safe given the release shipped with the phone. That information was for the standard Moto X. If the DE is unlocked, can I just go straight to rooting the phone? If the OTA updates won't work with root, is it best to accept the latest OTA pushes once my phone is online and then root? I want to be clear about what I've gained by getting the DE edition. Why go back to 4.4.2 if it ships with a later release?
I have no plans in the near future for changing ROM's. I'd just like to initially install what I am using on the Incredible - the clockworkmod recovery app (or current equivalent), titanium backuip, and a good tethering program. I currently use android wifi tether.
Thanks for any help.
dmm108 said:
My VZW Moto X DE is on its way to me, and I've spent a bunch of time on the forums yet still have the following questions and hope you can help. My current phone is an original Droid Incredible, which I rooted, mostly for recovery, backups, tethering, and system monitoring. This site was a great resource back when I did that and I greatly appreciated the information.
RE: the Moto X, I've read the steps for unlocking the bootloader and which paths for upgrading/downgrading are safe given the release shipped with the phone. That information was for the standard Moto X. If the DE is unlocked, can I just go straight to rooting the phone? If the OTA updates won't work with root, is it best to accept the latest OTA pushes once my phone is online and then root? I want to be clear about what I've gained by getting the DE edition.
I have no plans in the near future for changing ROM's. I'd just like to initially install what I am using on the Incredible - the clockworkmod recovery app (or current equivalent), titanium backuip, and a good tethering program. I currently use android wifi tether.
Thanks for any help.
Click to expand...
Click to collapse
I have a dev ed and keep mine the same way you intend... What I've gleaned so far is that the each update includes a new bootloader version that cannot be downgraded, i.e. if you take 4.4.2 you cannot downgrade to 4.4. At this point the VZW version only has 4.4.
As far as getting the phone to how you want it after you take the upgrades the material in the following two links should get you right where you want to be...
Custom recovery...
http://forum.xda-developers.com/showthread.php?t=2424110
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
He kind of muddied it up by adding other cleanup tools that I'm not interested in, if you're like me and only want the tether hack you will need to go to the 140.45.5 folder in his link and download xt1060-140.45.5-vzw-removal-s.zip He also has an undo zip that you might want to download and stash away just in case.
This part is speculative and potentially dangerous so take with a grain of salt and correct me if I'm wrong.
My understanding is that the big issue from the downgrade is that there will be a partition table mismatch if one takes an OTA upgrade and the phone will be bricked, though I can find nothing solid on this. Being that I plan on keeping a custom recovery I don't have to worry about accidentally taking an OTA and for some reason prefer to have the ability to downgrade, when 4.4.2 comes out I'm going to try to flash everything but the bootloader and I believe the partition table, (I need to read more and understand more before I speak with authority) to see if I can get away with it.
Also, on a side note, I found that freezing pre installed apps/bloat destroyed the wonderful battery life I was getting so I would suggest you keep your phone stock for a few days to get a feel for how the phone behaves before you begin freezing bloat.
Enjoy your new toy!
edthesped said:
I have a dev ed and keep mine the same way you intend... What I've gleaned so far is that the each update includes a new bootloader version that cannot be downgraded, i.e. if you take 4.4.2 you cannot downgrade to 4.4. At this point the VZW version only has 4.4.
As far as getting the phone to how you want it after you take the upgrades the material in the following two links should get you right where you want to be...
Custom recovery...
http://forum.xda-developers.com/showthread.php?t=2424110
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
He kind of muddied it up by adding other cleanup tools that I'm not interested in, if you're like me and only want the tether hack you will need to go to the 140.45.5 folder in his link and download xt1060-140.45.5-vzw-removal-s.zip He also has an undo zip that you might want to download and stash away just in case.
This part is speculative and potentially dangerous so take with a grain of salt and correct me if I'm wrong.
My understanding is that the big issue from the downgrade is that there will be a partition table mismatch if one takes an OTA upgrade and the phone will be bricked, though I can find nothing solid on this. Being that I plan on keeping a custom recovery I don't have to worry about accidentally taking an OTA and for some reason prefer to have the ability to downgrade, when 4.4.2 comes out I'm going to try to flash everything but the bootloader and I believe the partition table, (I need to read more and understand more before I speak with authority) to see if I can get away with it.
Also, on a side note, I found that freezing pre installed apps/bloat destroyed the wonderful battery life I was getting so I would suggest you keep your phone stock for a few days to get a feel for how the phone behaves before you begin freezing bloat.
Enjoy your new toy!
Click to expand...
Click to collapse
Thanks for that information. The last paragrapht seems counter-intuitive. I froze apps on the incredible so that it would reduce battery drain, why would freezing apps increase battery drain?
dmm108 said:
Thanks for that information. The last paragrapht seems counter-intuitive. I froze apps on the incredible so that it would reduce battery drain, why would freezing apps increase battery drain?
Click to expand...
Click to collapse
No idea, but freezing moto apps killed the battery. I haven't figured out what the culprit is yet as I'll be travelling this week and I don't want to jack up the phone while I'm on the road. I suspect another system app was spending effort looking for a missing app. Had I not ran my phone stock for a week I may have assumed that was just the phone as the high battery use was about the same as what I typically got on my S3. However, once I started freezing apps battery life went way down. Battery is good again after defrosting all Moto stuff that I assumed to be garbage. Once I get off the road I'll start freezing apps one at a time to see if I can isolate the culprit.
My thought is if you run it stock for a week you'll have a pretty good feel as to how the phone performs so you'll know whether your tweaks are helping or hurting you.
edthesped said:
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
Click to expand...
Click to collapse
Now that I'm looking at a full size computer I see that you are not getting a VZW version, The link above is not good! Sorry
edthesped said:
Now that I'm looking at a full size computer I see that you are not getting a VZW version, The link above is not good! Sorry
Click to expand...
Click to collapse
Yes, I am getting the Verizon DE. (VZW, 1st post).

[Q] Checking for OTA Update Error

Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).
mikestrong19 said:
Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).
Click to expand...
Click to collapse
Do NOT upgrade until you've read another 24 hours on this board!!!!! I think you should take a second look at your status and see if you misread 4.4.2 as 4.2.2
If I may ask, why not update?
mikestrong19 said:
If I may ask, why not update?
Click to expand...
Click to collapse
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.
doitinthedirt said:
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.
Click to expand...
Click to collapse
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.
mikestrong19 said:
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.
Click to expand...
Click to collapse
Wow, what a waste. You could have just flashed the entire STOCK SBF as per the Return to Stock thread, and avoided costing Moto money, and hence raising the prices for everybody... :/
This would have repaired any filesystem corruption/damage, which is the only conceivable thing that might have caused your issue.
Your new one will probably have 4.4.2....which means no write protection disabling.
D'oh!
---------- Post added at 07:17 PM ---------- Previous post was at 07:17 PM ----------
You could have had FULL root on 4.2.2.

[Q] New Verizon Moto X, Still on 4.2.2, Can't update

After trying all the latest and greatest, I'm back on the Moto X. Problem is, it came with 4.2.2 on it and I can't get it to update. It continually tells me either "An unexpected error has occurred. Please try again later." or another generic "can't do this right now" message that I can't recreate at the moment.
I have the latest OTA .zip, but that takes it from 4.4.2 to 4.4.4, so that won't do me much good yet. I'm trying to figure out the best way to do this... Either via old OTA .zip files, or I *am* comfortable using rsdlite and "sbfing" (fxz now right?). I'd rather do it via the OTA zip files, but if I have to I can do the fxz/sbf method. Any thoughts are appreciated!
Edit: also, if I end up having to use the fxz/sbf method, I'm assuming there are no issues with doing that for an update, rather than downgrading which has occasionally caused issues in the past depending on the version.
jntdroid said:
After trying all the latest and greatest, I'm back on the Moto X. Problem is, it came with 4.2.2 on it and I can't get it to update. It continually tells me either "An unexpected error has occurred. Please try again later." or another generic "can't do this right now" message that I can't recreate at the moment.
I have the latest OTA .zip, but that takes it from 4.4.2 to 4.4.4, so that won't do me much good yet. I'm trying to figure out the best way to do this... Either via old OTA .zip files, or I *am* comfortable using rsdlite and "sbfing" (fxz now right?). I'd rather do it via the OTA zip files, but if I have to I can do the fxz/sbf method. Any thoughts are appreciated!
Edit: also, if I end up having to use the fxz/sbf method, I'm assuming there are no issues with doing that for an update, rather than downgrading which has occasionally caused issues in the past depending on the version.
Click to expand...
Click to collapse
I have the same issue. Hopefully we will get an answeer soon.
tf442 said:
I have the same issue. Hopefully we will get an answeer soon.
Click to expand...
Click to collapse
I'm working through this right now: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
But I'm comfortable doing that as I've done it in the past.
tf442 said:
I have the same issue. Hopefully we will get an answeer soon.
Click to expand...
Click to collapse
jntdroid said:
I'm working through this right now: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
But I'm comfortable doing that as I've done it in the past.
Click to expand...
Click to collapse
You are completely correct. That (link) is the answer to your problem.
Just a quick update - using the link above and Samuri's tools, I got to 4.4.4 with no problems. I know if you're new to doing that stuff it can be a bit daunting, but if you read up on the thread above and the RSDFlasher thread he links to, it's pretty straightforward and does a lot of the work for you unlike the "old days".

Categories

Resources