dont get ota for marshmallow what i can do - X 2014 Q&A, Help & Troubleshooting

my moto dont get the ota
what i can do for have mm?
View attachment 3621870

You can check out the development sections and find one that fits your x

Try to take off sim card, reboot and put back sim. Some mentioned that they got the update like that lol

Related

[Q] most recent verizon software versions?

I rooted my phone via PwnMyMoto when I first got my Moto X. Then the OTA happened, and I held off on it until someone came out with a new root method (RockMyMoto). So I used the Moto X Toolkit to restore my recovery.img from a file titled "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml" and proceeded to take the OTA. However after my phone finished rebooting, I got an error message saying something to the effect of "the software update has failed!". But I checked my version #s and they seemed to be up-to-date with the OTA, and I can't pull any more software updates... and my root was gone. I then ran RockMyMoto and all the steps seemed to go smoothly. Can someone confirm that I have the right version #s?
Current: first attachment
"Status: Update Failed": second attachment
Thanks!
ikarios said:
I rooted my phone via PwnMyMoto when I first got my Moto X. Then the OTA happened, and I held off on it until someone came out with a new root method (RockMyMoto). So I used the Moto X Toolkit to restore my recovery.img from a file titled "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml" and proceeded to take the OTA. However after my phone finished rebooting, I got an error message saying something to the effect of "the software update has failed!". But I checked my version #s and they seemed to be up-to-date with the OTA, and I can't pull any more software updates... and my root was gone. I then ran RockMyMoto and all the steps seemed to go smoothly. Can someone confirm that I have the right version #s?
Current: first attachment
"Status: Update Failed": second attachment
Thanks!
Click to expand...
Click to collapse
idk what flashed and what didn't flash when you tried to take the ota but it doesn't seem to have flashed everything or maybe anything. Your FW is still .51 not .57 which is the ota FW version. restoring recovery might not have been enough because if your /system was changed by any rooted apps then the update would have failed (which is probably why it did). There are several options for how to take the ota, and you would benefit the most from learning how to use fastboot/adb instead of toolkits because then you will know what is done and what hasn't been done. you can also just flash the ota to your phone as well instead of taking through the phone itself. You will lose your data flashing it though. But if you want to take the ota, just flash recovery.img and system.img in fastboot and then put the "ota file" in your /cache folder. Do some reading and you can solve your problems and won't run into close to as many in the future because you will actually know whats going on with the phone instead of using toolkits for the phone.

Has the pure edition got 5.0 yet??

Has the Pure edition got the official OTA update to 5.0 yet? It seems At&t and Verizon have already gotten theirs 2 weeks ago, wasn't the pure edition supposed to be the first to get it? I thought that was the whole selling point of the pure edition...
It's just soke test.. Not the complete lollipop...
Sent from my XT1092 using XDA Free mobile app
It has been at least 2 weeks since it has been released. I got it on my pure edition.
Sent from my Nexus 6 using XDA Free mobile app
I have it on my pure edition. And I don't have it on my wifes AT&T Moto X. Not a big deal to sideload it or wait until it has less bugs. There is a simple solution...= SIDELOAD!!!
falcon26 said:
Has the Pure edition got the official OTA update to 5.0 yet? It seems At&t and Verizon have already gotten theirs 2 weeks ago, wasn't the pure edition supposed to be the first to get it? I thought that was the whole selling point of the pure edition...
Click to expand...
Click to collapse
I'll be waiting on the OTA update to be delivered by .... OTA. I'm following this thread to try to find out when the updates start getting pushed out over air... By now, everyone must know there is a flashable version available but if you're like me you feel no need to root unlock and flash as this device works just fine as is. The Pure editions should be the first to receive the pushed updates, I'm waiting on them for two handsets...
elpmet27 said:
I'll be waiting on the OTA update to be delivered by .... OTA. I'm following this thread to try to find out when the updates start getting pushed out over air... By now, everyone must know there is a flashable version available but if you're like me you feel no need to root unlock and flash as this device works just fine as is. The Pure editions should be the first to receive the pushed updates, I'm waiting on them for two handsets...
Click to expand...
Click to collapse
i'm in the same situation as yours, i know, it's annoying, i want to get lollipop on my pure edition moto x, i live in colorado if that's gonna help.
i had many chats with motorola about the update and they told me that the update is being sent in patches, seems that you and me are not lucky enough to be in the first patches that receive lollipop
i just hope we'll be getting the update soon.
i check for the update more than once day in hope of getting it but there is nothing
but at least you're not the only one suffering from this, you and me are in the same boat buddy
I don't understand how at&t and Verizon have gotten the ota 5.0 update yet the pure edition hasn't how is that possible?
elpmet27 said:
I'll be waiting on the OTA update to be delivered by .... OTA. I'm following this thread to try to find out when the updates start getting pushed out over air... By now, everyone must know there is a flashable version available but if you're like me you feel no need to root unlock and flash as this device works just fine as is. The Pure editions should be the first to receive the pushed updates, I'm waiting on them for two handsets...
Click to expand...
Click to collapse
you dont need root to sideload the update
you just need to either copy the update file to the internal storage
power off your phone, and go into bootloader/fastboot mode (power and volume down)
then go to recovery, select apply update from sdcard
or follow the same steps except copying the files, you choose apply update from sideload
connect your moto x to the computer via micro usb
and use this command in command prompt/terminal window
adb sideload <update-file.zip>
and the update should install successfully (must be unrooted)
We shouldn't have to side load anything. The update should have been on our phones long before the At&t or Verizon one. That was the whole point of the pure edition wasn't it, to get updates much faster OTA then the carrier branded Moto X? Apparently not. Had I known that it's not the case I would have just gotten the carrier branded one...
AgentChaos said:
you dont need root to sideload the update
you just need to either copy the update file to the internal storage
power off your phone, and go into bootloader/fastboot mode (power and volume down)
then go to recovery, select apply update from sdcard
or follow the same steps except copying the files, you choose apply update from sideload
connect your moto x to the computer via micro usb
and use this command in command prompt/terminal window
adb sideload <update-file.zip>
and the update should install successfully (must be unrooted)
Click to expand...
Click to collapse
I understand the idea of ADB side loading, and the device doesn't need to be rooted in order to do this. It shouldn't be necessary.... I see several messages per week from people who have soft bricked their phones, or worse. Usually people Flashing updates from risky sources, or the wrong versions.
The OTA update from T-Mobile is being delayed for some reason, whether it'd be to fix bugs or some other reason. Why would I flash some preliminary version only to have to flash back to 4.4.5 to get the OTA update.. Something is wrong with this picture....
What have I missed? Android 5.0 was or has been rolling out on pure edition for 2 weeks now:
http://motorola-blog.blogspot.com/2...p-android-5-lollipop.html?linkId=10507079&m=1
Sent from my Nexus 6 using XDA Free mobile app
I got mine within hours.

[Q] Grabbing OTA Update

Hi,
I've recently received the OTA update notification for my Moto X (telcel, Mexico) to android 4.4.4. I would like to have the package in case I ever need to go back to stock, and since sbf droid appears to be down for now, I can't think of where I could get this image.
I tried dumping a logcat but I can't seem to locate the download link, I was wondering if anyone with more experience on the matter could help me out getting the firmware image.
I'm attaching the logcat file.
Thanks for you time reading this / helping me out!
The link probably won't show up in logcat until you're actually downloading the update. Also, the OTA is only a diff from whatever you're on now to 4.4.4, it isn't a full flashable image.
Sent from my Moto X
imnuts said:
The link probably won't show up in logcat until you're actually downloading the update. Also, the OTA is only a diff from whatever you're on now to 4.4.4, it isn't a full flashable image.
Sent from my Moto X
Click to expand...
Click to collapse
That makes sense since the download was on the small side. I guess then there's really not much holding me back from rooting now.
Thanks!

Can't update to Lollipop (xt1064)

Got my mom a Moto G for Christmas and I'm trying to get it to lollipop before I give it to her. I found the 1064 image. But it doesn't seem to want to flash. It gives a software error. Photo linked
Never rooted
Never unlocked.
cammykool said:
Got my mom a Moto G for Christmas and I'm trying to get it to lollipop before I give it to her. I found the 1064 image. But it doesn't seem to want to flash. It gives a software error. Photo linked
Never rooted
Never unlocked.
Click to expand...
Click to collapse
Have you found the answers..if not
Go here will help >> http://forum.xda-developers.com/showthread.php?p=56689412
If you cannot work it out, PM and I will help..you will need a computer and working knowledge, of using adb..if you cannot update via the device..then adb is the only way..
Sent from my:
4.4.4_23.3.24 XT1080M
Droid Maxx Developer Edition
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Same exact issue as OP... bought Moto G 2014 for mom for X-mas, toying with it today and it thinks it is up to date.. try to sideload like OP and get the exact same error... my guess is update is for version 21.11.17 and the phone came with 21.11.23 preinstalled. Maybe needs a cell network to realize it needs it? (I don't have a SIM in it, it is going to replace mom's current phone & number). OP did you put a SIM in yours? (even though that shouldn't matter...)
XT-1063 from the 149.99 Amazon Sale here too.
I get this when sideloading update:
Package expects build fingerprint of motorola/titan_retuglb/titan_umts:4.4.4/KXB21.85-17/14:user/release-keys or motorola/titan_retuglb/titan_umts:5.0/LXB22.39-6:user/release-keys; this device has motorola/titan_retuglb/titan_umts:4.4.4/KXB21.85-23/21:u Installation aborted.
archvile7 said:
Same exact issue as OP... bought Moto G 2014 for mom for X-mas, toying with it today and it thinks it is up to date.. try to sideload like OP and get the exact same error... my guess is update is for version 21.11.17 and the phone came with 21.11.23 preinstalled. Maybe needs a cell network to realize it needs it? (I don't have a SIM in it, it is going to replace mom's current phone & number). OP did you put a SIM in yours? (even though that shouldn't matter...)
Click to expand...
Click to collapse
Yes. It's active and all is well. Minus the ota of course.
I saw a thread on reddit where the update was put on hold due to a memory leak. Not sure how accurate that is but would line up with reports of a second OTA received by some users after the main lollipop update. Hopefully they'll get it out before Xmas.
I'm giving my moms to her on the 19th
Yeah i'm in the same boat. The ota's you can sideload are for firmware 21.11.17 and my phone's firmware is 21.11.23. The only solution I found was to follow this guide. http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167. Basically you unlock bootloader, restore to stock 4.4.4. (with the 21.11.17 version), then you sideload the lollipop ota. It's too much of a hassle so I'll just wait.
Anyone in here got the OTA?
Still waiting for it.
Customer support claimed they are only in soak testing at the moment, i am sure 5.0.1 will drop soon like all the other lollipop updates.
But I have a 5.0 update image?
Still waiting for 1068
Just got my Moto G and checking obsessively every few hours for the OTA update to Lollipop. Hurry, Moto, hurry!
JShan said:
Just got my Moto G and checking obsessively every few hours for the OTA update to Lollipop. Hurry, Moto, hurry!
Click to expand...
Click to collapse
you might wanna stop doing that lol
Gabboplano said:
you might wanna stop doing that lol
Click to expand...
Click to collapse
Yeah, I did more research and saw some messages from people who had called Motorola to say that it's not coming until late December or January.
JShan said:
Yeah, I did more research and saw some messages from people who had called Motorola to say that it's not coming until late December or January.
Click to expand...
Click to collapse
Meh don't trust them, a while back they said we'd be all updated by December 4th

[Q] OTA Requires Carrier Approval ?

My new N6 (Google Play Store) with a Verizon sim card has not been offered the 5.1 update OTA. It was offered the 5.01 OTA update on first boot. I ran across the following statement on the web.
As for who handles updates, it all comes from Google, no matter what. However, Google will withhold updates based on SIM card pending carrier approval. AT&T has not approved Android 5.1 yet, and therefore, anyone with an AT&T SIM card in their Nexus 6, no matter where it was purchased, will not be offered the OTA until AT&T approves it. So far, the only US carriers to approve Android 5.1 are T-Mobile and Sprint.
Click to expand...
Click to collapse
So, has any non-branded Verizon N6 received the 5.1 OTA yet? Please exclude any "forced" or manual OTAs.
I was hoping that at last my carrier would not interfere with updates.
Thanks ...
clairez said:
I was hoping that at last my carrier would not interfere with updates.
Thanks ...
Click to expand...
Click to collapse
Yeah this is a new thing. Ridiculous. Its never been tied to SIM provision before.
clairez said:
My new N6 (Google Play Store) with a Verizon sim card has not been offered the 5.1 update OTA. It was offered the 5.01 OTA update on first boot. I ran across the following statement on the web.
So, has any non-branded Verizon N6 received the 5.1 OTA yet? Please exclude any "forced" or manual OTAs.
I was hoping that at last my carrier would not interfere with updates.
Thanks ...
Click to expand...
Click to collapse
Based on recollection, a few. But not many. And yes, AT&T is definately trying to control updates. I suspect Verizon will, too.
Based on the following article, I doubt that you will ever get a Verizon specific OTA on your device > http://www.androidpolice.com/2015/0...te-one-that-wasnt-purchased-from-the-carrier/
No mine would only update to 5.01. GPS N64.
Maybe pull Sim card reboot and check via only WiFi?
dahlem said:
Maybe pull Sim card reboot and check via only WiFi?
Click to expand...
Click to collapse
You might get D this way, but not E.
dahlem said:
Maybe pull Sim card reboot and check via only WiFi?
Click to expand...
Click to collapse
That didn't work for me - I had to also perform a factory reset to get the "D" OTA (tried this yesterday). I'm on Verizon with a Nexus 6 bought directly from Motorola.
At least this thread sort of answers my question posed in the linked post above. However, I'm wondering if there's something on the phone we can "clear" (so to speak) after removing the SIM in order to help trigger OTAs from Google, bypassing carrier interference.
I've been thinking of staying stock for awhile, due to expectations of quick-from-Google OTAs . . . but, this is driving me to consider custom ROMs and not looking back.
- ooofest
ooofest said:
However, I'm wondering if there's something on the phone we can "clear" (so to speak) after removing the SIM in order to help trigger OTAs from Google, bypassing carrier interference.
Click to expand...
Click to collapse
I'm not sure about this, but when you pull your SIM, I think Google sees it as a generic N6 via WiFi. So if you do generate an OTA download, it's the general one.
I wonder if you have to put another SIM card in. I know in Play, my device shows as a carrier, even though its a play store device. I imagine you'd have to use another sim in it to allow that sim to be "registered" with Google, to "overwrite" the previous one. I doubt there is anything you can clear to do that.
Pulling The String !
What I have learned so far ( rest of you gals/guys already know this! ) is that one has to be very careful with the information in these/all forums.
There are users who say they have received the automatic 5.1 OTA with a non VZ branded phone ( both GPS and Motorola variants ). But when you start to pull the string with more questions, answers start to become vague. And why people post information that is not factual is the subject of another post.
My experience at this point is as follows. With a Verizon nano sim in the N6, I will not receive any OTAs, now or in the future. The reason is not clear at this time. It may be because the N6 is listed as a non-VZ phone in Verizon's system. Which, in turn, may be caused by the IMEI not being registered in Verizon's database. All conjecture at this point. ( More factual information required )
What is clear to me is that Motorola and Google should post a warning about the N6 not being compatible with Verizon (presently). And recommend purchase of the N6 directly from Verizon. Not holding my breath on this one !
Back to the problem at hand. I have tried the various suggestions.
1. Removing the VZ sim and connecting via wifi does NOT produce an OTA (5.1) offer.
2. Removing the VZ sim and connecting via wifi and doing a factory reset DOES produce an OTA (5.1) offer. This requires a backup/restore of user data. Follow this procedure exactly:
a. Backup your Nexus 6 (go to “settings” >> “backup & reset” >> select an account to back-up by clicking on “backup” and selecting the account you want to backup)
b. Remove your SIM card (while the phone is on)
c. Reset your Nexus 6 (go to “settings” >> “backup & reset” >> “factory reset data”)
d. Restore your Nexus 6 during set-up but DO NOT insert your SIM card
e. At the end of the setup, you should be offered the 5.1 update
d. Download (~450MB) will take awhile dependent on connection speed
e. After download is complete, press the "restart and install" button
f. Android icon with spinning symbol during install system update ( 3-5 minutes)
g. N6 will restart automatically (Optimizing apps 126)
h. Home screen, Settings --> About phone --> Build number, LMY47D --> Version 5.1
But, this approach, for me, would be too onerous for future/routine OTAs. My purpose behind purchasing the N6 was the timely, automatic delivery of OTAs by Google without carrier interference. The referenced article by the Android Police may be the reality. The ultimate solution is of course with Verizon, which leaves me with an uncomfortable feeling.
As always, thanks for the help ...
@clairez,
Very good post, and summarized very concisely.
I got mine thru VZ, this is most likely the only time I'll ever say this about them - At least they released it, though being late to the party, with 5.1 already installed.
(I feel so bad for those who may have bricked trying the OTA or image and running into issues ...)
As to how they will affect us moving forward, I'm crossing my fingers, but while I hate it, let me play devil's advocate here, they didn't place a boot animation, sounds, or other oem crap on it, there are the small system services, but that's the same amongst all of the N6's. and the tramp stamp was easily removed aka ATT's.
So far, it could have been way worse as far as getting one from VZ, but I feel for you guys that had it early and are now waiting on them to get an OTA, or even have the unit register correctly on their systems.
But the overall answer to the overall thing, is that if they did hold up updates down the road, we do what any crackflasher would, flash the image when released, right? Why we got the thing in the first place
This emerging situation where carriers apparently delay our Nexus 6 OTA timings is leading me to stay on the flashing path.
Running stock and locked 5.1 E for now, might just run unlocked and accept potential decrease in local security to minimize danger in future flashes. I like stock so far, but being unlocked will probably tempt me to root and try custom ROMs, I expect.
If Verizon wanted us to stay on the pure OTA path with this phone, they don't appear to be showing that intent.
- ooofest
clairez said:
What I have learned so far ( rest of you gals/guys already know this! ) is that one has to be very careful with the information in these/all forums.
There are users who say they have received the automatic 5.1 OTA with a non VZ branded phone ( both GPS and Motorola variants ). But when you start to pull the string with more questions, answers start to become vague. And why people post information that is not factual is the subject of another post.
My experience at this point is as follows. With a Verizon nano sim in the N6, I will not receive any OTAs, now or in the future. The reason is not clear at this time. It may be because the N6 is listed as a non-VZ phone in Verizon's system. Which, in turn, may be caused by the IMEI not being registered in Verizon's database. All conjecture at this point. ( More factual information required )
What is clear to me is that Motorola and Google should post a warning about the N6 not being compatible with Verizon (presently). And recommend purchase of the N6 directly from Verizon. Not holding my breath on this one !
Back to the problem at hand. I have tried the various suggestions.
1. Removing the VZ sim and connecting via wifi does NOT produce an OTA (5.1) offer.
2. Removing the VZ sim and connecting via wifi and doing a factory reset DOES produce an OTA (5.1) offer. This requires a backup/restore of user data. Follow this procedure exactly:
a. Backup your Nexus 6 (go to “settings” >> “backup & reset” >> select an account to back-up by clicking on “backup” and selecting the account you want to backup)
b. Remove your SIM card (while the phone is on)
c. Reset your Nexus 6 (go to “settings” >> “backup & reset” >> “factory reset data”)
d. Restore your Nexus 6 during set-up but DO NOT insert your SIM card
e. At the end of the setup, you should be offered the 5.1 update
d. Download (~450MB) will take awhile dependent on connection speed
e. After download is complete, press the "restart and install" button
f. Android icon with spinning symbol during install system update ( 3-5 minutes)
g. N6 will restart automatically (Optimizing apps 126)
h. Home screen, Settings --> About phone --> Build number, LMY47D --> Version 5.1
But, this approach, for me, would be too onerous for future/routine OTAs. My purpose behind purchasing the N6 was the timely, automatic delivery of OTAs by Google without carrier interference. The referenced article by the Android Police may be the reality. The ultimate solution is of course with Verizon, which leaves me with an uncomfortable feeling.
As always, thanks for the help ...
Click to expand...
Click to collapse
thank you for your helpful post!
i just had a few clarifying questions. my current setup is 5.01 with an unlocked bootloader, rooted phone and twrp recovery.
in order for me to be able to accept the OTA update, i have to flash the stock image and stock recovery, unroot, and relock my phone. is that correct?
gunit34328 said:
thank you for your helpful post!
i just had a few clarifying questions. my current setup is 5.01 with an unlocked bootloader, rooted phone and twrp recovery.
in order for me to be able to accept the OTA update, i have to flash the stock image and stock recovery, unroot, and relock my phone. is that correct?
Click to expand...
Click to collapse
You don't need to re-lock your bootloader. Otherwise, yes on the others.
Evolution_Freak said:
You don't need to re-lock your bootloader. Otherwise, yes on the others.
Click to expand...
Click to collapse
thank you for your reply!
gunit34328 said:
thank you for your reply!
Click to expand...
Click to collapse
No problem at all.
just wanted to give my experience...
bought a nexus 6 from best buy last week and it came with 5.0 installed. right away it took a 5.0.2 update but nothing after that. I had to manually flash the 5.1 "E" build on it, which I did because I'm on verizon and felt it was the best to be on
dansan382 said:
just wanted to give my experience...
bought a nexus 6 from best buy last week and it came with 5.0 installed. right away it took a 5.0.2 update but nothing after that. I had to manually flash the 5.1 "E" build on it, which I did because I'm on verizon and felt it was the best to be on
Click to expand...
Click to collapse
Are you sure it was 5.0.2 ??? Should have been 5.0.1 no? Anyway, good job getting updated anyway. :good: Yes, Verizon users should be on E.
Evolution_Freak said:
Are you sure it was 5.0.2 ??? Should have been 5.0.1 no? Anyway, good job getting updated anyway. :good: Yes, Verizon users should be on E.
Click to expand...
Click to collapse
im sorry, you're right.. it was 5.0.1 because it was LRX22C.. my bad.

Categories

Resources