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.
Related
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).
I updated to 4.4.2 on my Verizon Developer Edition today and now I'm having issues updating Cloud Print. The Play Store keeps telling me that the package wasn't signed correctly. Do I have any other options besides rooting, uninstalling and then reinstalling it, because it's a system app? Any clues would be really appreciated. I'd post an image, but I'm too new of a user to link to one.
FinalBabality said:
I updated to 4.4.2 on my Verizon Developer Edition today and now I'm having issues updating Cloud Print. The Play Store keeps telling me that the package wasn't signed correctly. Do I have any other options besides rooting, uninstalling and then reinstalling it, because it's a system app? Any clues would be really appreciated. I'd post an image, but I'm too new of a user to link to one.
Click to expand...
Click to collapse
I recommend the basics. Going to the settings and clearing the app cache for the play store, try factory reset (yeah i know it sucks) try downloading the app again on wifi on LTE, etc. etc.
drago10029 said:
I recommend the basics. Going to the settings and clearing the app cache for the play store, try factory reset (yeah i know it sucks) try downloading the app again on wifi on LTE, etc. etc.
Click to expand...
Click to collapse
I've tried all of it and can't seem to sort it out. Think I'll just leave it alone, seeing as I've yet to print from any if my mobile devices. I did apply the update myself and I wonder if that has anything to do with it.
Sent from my XT1060 using Tapatalk
If you applied 4.4.2 from the files available here at XDA unfortunately you don't have the equivalent to a true OTA. The Cloud Print included with it had been modified and you will not be able to update it unless you root, delete it and reinstall it from the play store. The full image file from droid-developers.org has the exact same issue. Very frustrating punishment for those of us who weren't patient enough to wait for the OTA.
jpizz said:
If you applied 4.4.2 from the files available here at XDA unfortunately you don't have the equivalent to a true OTA. The Cloud Print included with it had been modified and you will not be able to update it unless you root, delete it and reinstall it from the play store. The full image file from droid-developers.org has the exact same issue. Very frustrating punishment for those of us who weren't patient enough to wait for the OTA.
Click to expand...
Click to collapse
droid-developers doesn't even have a Verizon 4.4.2 sbf file.
Steve-x said:
droid-developers doesn't even have a Verizon 4.4.2 sbf file.
Click to expand...
Click to collapse
Sorry, I was referring to the GSM Dev Edition. Same exact problem.
jpizz said:
If you applied 4.4.2 from the files available here at XDA unfortunately you don't have the equivalent to a true OTA. The Cloud Print included with it had been modified and you will not be able to update it unless you root, delete it and reinstall it from the play store. The full image file from droid-developers.org has the exact same issue. Very frustrating punishment for those of us who weren't patient enough to wait for the OTA.
Click to expand...
Click to collapse
Alright I figured it had something to do with the fact I installed it from Zip instead of waiting for the OTA. I tried that solution and that didn't work either. When I installed it with root and the tried to install from the Play Store, it just told me "Invalid Package." So I'll wait a little while, until it's solidly rolled out and then go back to 4.4 and then flash the OTA the official way. Thanks for the confirmation on the Zip being the issue. Not having any other issues though, so I might just stick it out.
FinalBabality said:
Alright I figured it had something to do with the fact I installed it from Zip instead of waiting for the OTA. I tried that solution and that didn't work either. When I installed it with root and the tried to install from the Play Store, it just told me "Invalid Package." So I'll wait a little while, until it's solidly rolled out and then go back to 4.4 and then flash the OTA the official way. Thanks for the confirmation on the Zip being the issue. Not having any other issues though, so I might just stick it out.
Click to expand...
Click to collapse
If you have updated to 4.4.2 then you cannot downgrade back to 4.4.
Steve-x said:
If you have updated to 4.4.2 then you cannot downgrade back to 4.4.
Click to expand...
Click to collapse
Have a dev edition with an unlocked bootloader. I've already done it once to try and fix this issue.
FinalBabality said:
Have a dev edition with an unlocked bootloader. I've already done it once to try and fix this issue.
Click to expand...
Click to collapse
Well you must have manually flashed 4.4 without the 4.4 bootloader then, because RSD wont allow you to flash from 4.4.2 down to 4.4.
Be careful because if you take an update while back on 4.4 you will hard brick your phone.
mastarifla said:
Well you must have manually flashed 4.4 without the 4.4 bootloader then, because RSD wont allow you to flash from 4.4.2 down to 4.4.
Be careful because if you take an update while back on 4.4 you will hard brick your phone.
Click to expand...
Click to collapse
Yeah that's exactly what I did, that's a good point. So should I wait for Motorola to post the recovery files, and then flash that when it comes out? Would that be safer?
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.
So i keep being prompted to get the new OTA update and whenever i try to download and install it, it reboots goes to the install screen, gets about 1/4 of the way through, says error and then reboots to an update unsuccessful page
After digging around my phone i also noticed it says my software was modified on the status page
But obviously ive never rooted this phone as its pretty much impossible at the moment
Has anyone experienced something similar and found a way to fix it?
did you disable any of the bloat? that might be your issue.....
xbxjunkie said:
did you disable any of the bloat? that might be your issue.....
Click to expand...
Click to collapse
I did! I'll re enable it all and see if it fixes the issue
jaideng123 said:
So i keep being prompted to get the new OTA update and whenever i try to download and install it, it reboots goes to the install screen, gets about 1/4 of the way through, says error and then reboots to an update unsuccessful page
After digging around my phone i also noticed it says my software was modified on the status page
But obviously ive never rooted this phone as its pretty much impossible at the moment
Has anyone experienced something similar and found a way to fix it?
Click to expand...
Click to collapse
Try a factory data reset but you will wipe your phone and lose all data and apps.
xbxjunkie said:
did you disable any of the bloat? that might be your issue.....
Click to expand...
Click to collapse
That's odd, I even blocked the OTA via adb and mine says official.
OK i tried both, neither worked, also when i boot into recovery i get qe 1/1 at the bottom left side of my screen
Decided to just get a replacement from motorola since I'm still under warranty, but thank you for the suggestions!
jaideng123 said:
Decided to just get a replacement from motorola since I'm still under warranty, but thank you for the suggestions!
Click to expand...
Click to collapse
You could just flash the stock ROM again!
Gundabolu SC said:
You could just flash the stock ROM again!
Click to expand...
Click to collapse
I am unable to obtain the moforoot util to do this. When I put in my ID on the moforoot page, it says my device is not supported. I know for a fact the model and current OS on it. Its 5.1 updated already which is probably why the website is rejecting my request to obtain the util.
I do not think the bootloader will allow me to downgrade. If anybody has a solution, please let me know.
Note: Using XT1254 w/ latest 5.1 update from Aug-Sept.
LatencyXXX said:
I am unable to obtain the moforoot util to do this. When I put in my ID on the moforoot page, it says my device is not supported. I know for a fact the model and current OS on it. Its 5.1 updated already which is probably why the website is rejecting my request to obtain the util.
I do not think the bootloader will allow me to downgrade. If anybody has a solution, please let me know.
Note: Using XT1254 w/ latest 5.1 update from Aug-Sept.
Click to expand...
Click to collapse
If you want to flash an official update that is greater than or equal to the version you're on now, you don't need mofo. You could use fastboot, rsdlite, Motorola device manager or the Verizon upgrade assistant. The upgrade assistant is probably the easiest way to go. That's the annoying pop up software you get whenever you plug your phone into your computer.
TheSt33v said:
If you want to flash an official update that is greater than or equal to the version you're on now, you don't need mofo. You could use fastboot, rsdlite, Motorola device manager or the Verizon upgrade assistant. The upgrade assistant is probably the easiest way to go. That's the annoying pop up software you get whenever you plug your phone into your computer.
Click to expand...
Click to collapse
I tried all 3 different options and none of them work. Then I went into Verizon store and asked them to do it and they told me that they don't do that anymore. Only contacts, photos, etc.
The store told me to send it to Motorola for them to do it. I'm sure there is an ISP somewhere or some trick button internally for them to unlock the bootloader, but nobody is saying.
I am out of options, and I am ready to send it to whomever can fix it for me. PM me if you can guarantee to do it and send it back.
-Thanks
LatencyXXX said:
I tried all 3 different options and none of them work. Then I went into Verizon store and asked them to do it and they told me that they don't do that anymore. Only contacts, photos, etc.
The store told me to send it to Motorola for them to do it. I'm sure there is an ISP somewhere or some trick button internally for them to unlock the bootloader, but nobody is saying.
I am out of options, and I am ready to send it to whomever can fix it for me. PM me if you can guarantee to do it and send it back.
-Thanks
Click to expand...
Click to collapse
Send it to Motorola then. If your phone is less than a year old, they will send you a new one for free.
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
carrot34 said:
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
Click to expand...
Click to collapse
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Evolution_Freak said:
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Click to expand...
Click to collapse
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
carrot34 said:
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
Click to expand...
Click to collapse
Are you familiar with sideload?
---------- Post added at 09:42 PM ---------- Previous post was at 09:37 PM ----------
Check out my thread on OTA's.
http://forum.xda-developers.com/showthread.php?t=2992919
In post #2, there's a link to the OTA files thread. Take the one that is specifically for T-Mobile. LRX22C to LMY47M.
Evolution_Freak said:
Are you familiar with sideload?
Click to expand...
Click to collapse
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
carrot34 said:
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
Click to expand...
Click to collapse
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Evolution_Freak said:
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Click to expand...
Click to collapse
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
carrot34 said:
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
Click to expand...
Click to collapse
Yes, you want the LRX22C to LMY47M OTA as I said before. No, you don't need to worry about it not being on the images page. Also a no for it affecting your ability to get OTA's in the future. On a Nexus, this is pretty much as official as getting the OTA natively.
OK, an update: got an error installing the update any way I tried, even after a factory reset. Called Google support, and they're replacing the phone for me.