My girlfriend just got a Moto X from the holiday sale last week. She bought an AT&T branded devices so she could use it on Straight Talk.
It works fine on the network, but the OTA updates would just not work at ALL. Every time it wanted to update, it would ask to be on the wi-fi network, which it already was. And if we ever got a progress bar, it just said "Will Resume when on Wi-Fi" and showed a 0% progress for over an hour.
Motorola support was utterly useless, they hung up on us, TWICE, after 2+ hours of phone calls, and the third time the level two technician, who we were told could force the update, told us we could factory reset the phone to make it work.
After THAT failed, he told us we could just mail it back to Motorola and they'd install the update themselves. At that point I just used RSD Lite to flash the 4.4 stock firmware, because it was much faster than waiting two weeks for the same thing. Now I'm not sure if the OTA updates are working still, but she's been unable to download the new boot services or active notifications apps, which makes me thing there are still problems with it.
Anyone else have these issues with OTA updates? Specifically with the AT&T variant?
Anything would be helpful!
I am having the same problem on an AT&T model purchased from the holiday sale. I tried the factory reset suggestion and that didn't work. I am actually on the phone with level two support right now hoping for a solution. I will post a follow up if anything works to resolve this issue.
I updated two Moto X's to 4.4 with no problems at the beginning of the month, but I had this same issue this past weekend when my latest Moto X arrived and I tried to update it. I finally got the update to download by tethering to my other phone instead of using my home Wi-Fi. Sucked that it used my AT&T data, but at least it worked. I researched it a bit and apparently some Motorola Android phones have had this issue before. Others said it will eventually download if you just leave it, but it could take a while. Pretty sure it's an issue with Motorola's update servers because a bunch of people will report it at once and factory resetting doesn't help.
I haven't had this issue but you can always just download the OTA manually and sideload it with adb.
Sent from my Moto X
gtg465x said:
I updated two Moto X's to 4.4 with no problems at the beginning of the month, but I had this same issue this past weekend when my latest Moto X arrived and I tried to update it. I finally got the update to download by tethering to my other phone instead of using my home Wi-Fi. Sucked that it used my AT&T data, but at least it worked. I researched it a bit and apparently some Motorola Android phones have had this issue before. Others said it will eventually download if you just leave it, but it could take a while. Pretty sure it's an issue with Motorola's update servers because a bunch of people will report it at once and factory resetting doesn't help.
Click to expand...
Click to collapse
Okay, as much as it sucks, it's somewhat comforting to hear that others are having the issue as well.
Since it was new out of box, and all Moto Support wanted to do was install it at their factory, we just used RSD Lite and pushed the 4.4 factory image.
_MetalHead_ said:
I haven't had this issue but you can always just download the OTA manually and sideload it with adb.
Sent from my Moto X
Click to expand...
Click to collapse
We just wound up flashing the 4.4 Factory Image from RSD Lite in the end. Is there a good repo for OTA zips for ATT though? I found one for an earlier update listed here in XDA (the one that brought some camera fixes), but I couldn't find any other stock OTA zips that could be applied via stock recovery outside of that one.
soxfan37 said:
I am having the same problem on an AT&T model purchased from the holiday sale. I tried the factory reset suggestion and that didn't work. I am actually on the phone with level two support right now hoping for a solution. I will post a follow up if anything works to resolve this issue.
Click to expand...
Click to collapse
If support doesn't help (they were pretty sucky towards us), you can use RSD Lite to apply the factory 4.4 image to the phone without any modifications
Tmobile version not updating either
I have the Tmobile variant. Its not taking the update either. Two different ways its prompting and not working. The first is I have a notification that the update will begin when I'm on wifi. I'm on wifi and it never starts. After reboot, I check the 'about phone', --system updates. "It tells me an update is currently being downloaded. You will be notified when the download is complete."
Waiting and waiting.....
After my second call yesterday, level two escalated me to level three. They called me this morning, (they don't take incoming calls) and the rep pushed the update to my phone. It took about 10 minutes and then the update started downloading. After a reboot I was then able to download the kitkat update. So now all is well. One of the reps at level two said he tried pushing the update to me (on Monday) but it didn't work. I guess level three has more power. Anyway, it did resolve my issue.
Good luck to the rest of you with this problem and Happy Holidays to the community.
My wife took her phone to work and connected to wifi there...update came through. I'm guessing either motorola servers cleared up, or needed a different wifi...but either way, resolved.
FYI, I am a new Android user.
Two weeks ago I got the Nexus 6 from T-Mobile. When I first got the phone there were no updates available for the phone. And I know at that time only version 5.0.1 was out, and it won't update that. And since then I haven't received an update for the phone. When version 5.1 was release I was excited to update. The phone tells me that my phone is up to date every time I check it throughout the day. My phone is still running version 5.0.
I did see that the update(5.1) was available when I erased my phone. I had no accounts signed in to the phone and I prevented anything to update except 5.1, but it went away and never downloaded.
I have forced stopped "Google Services Framework" multiple times and deleted the information, restarted the phone, and still no update.
I have called T-Mobile tech support to get help from them and they sent me a new phone, and still no luck.
What can I do to get the update? Is it possible that the SIM card I am using is from my iPhone 6 is preventing this?
I see that everyone is downloading updates and side loading them, but all the guides are pretty vague. I am on a Macbook so I don't understand the commands, but I do know how to use the terminal. I would like to stay away from side loading because my lack of experience.
Just be patient
The update comes out in waves, some get it later then others. You'll get it eventually
First, look here:
http://www.droid-life.com/2013/11/2...or-updates-on-nexus-devices-isnt-helping-you/
Also, try pulling out your Sim card and rebooting the phone. Let it sit without Sim and see if update returns.
I bought this phone over the Note 4 because of permanent root capability.
Now I'm finding that AT&T locked the bootloader and locked down rooting.
Is it even possible or do I now own a piece of junk?
I hate touchwiz, I wanna install a real rom...
changoland said:
I bought this phone over the Note 4 because of permanent root capability.
Now I'm finding that AT&T locked the bootloader and locked down rooting.
Is it even possible or do I now own a piece of junk?
I hate touchwiz, I wanna install a real rom...
Click to expand...
Click to collapse
If it's already on stock 5.0, then yes. Currently no root methods avaliable.
nutt_case said:
If it's already on stock 5.0, then yes. Currently no root methods avaliable.
Click to expand...
Click to collapse
That sucks, I assumed at first that it came out of the box at 5.0, but it must have updated to 5.0 when it restored all my apps through Google during initial setup. Word to the wise: Don't sign into Google on your first boot if you ever want to root this phone! I never had the opportunity, now I've gotta sell a brand new phone, ugh
changoland said:
That sucks, I assumed at first that it came out of the box at 5.0, but it must have updated to 5.0 when it restored all my apps through Google during initial setup. Word to the wise: Don't sign into Google on your first boot if you ever want to root this phone! I never had the opportunity, now I've gotta sell a brand new phone, ugh
Click to expand...
Click to collapse
Not to rub it in, but since other people may read your advice: It is not google or restoring the application that upgraded the phone to 5.0. You most likely got an OTA (over the air update) notice from AT&T which prompted you to update, then you did it, and updated your phone to lollipop.
najoor said:
Not to rub it in, but since other people may read your advice: It is not google or restoring the application that upgraded the phone to 5.0. You most likely got an OTA (over the air update) notice from AT&T which prompted you to update, then you did it, and updated your phone to lollipop.
Click to expand...
Click to collapse
Not to contradict you and come off like an asshole, but that is exactly how I got the 5.0 update. It was fresh out of the box and asked me if I wanted to restore content from my previous phone. I was never prompted for an OTA update and I never in a million years would have ever accepted or agreed to that. I'm just trying to warn anybody else who might end up in the same position I ended up in.
changoland said:
Not to contradict you and come off like an asshole, but that is exactly how I got the 5.0 update. It was fresh out of the box and asked me if I wanted to restore content from my previous phone. I was never prompted for an OTA update and I never in a million years would have ever accepted or agreed to that. I'm just trying to warn anybody else who might end up in the same position I ended up in.
Click to expand...
Click to collapse
I'm sorry, I am not questioning your judgment about this and as always I would like to be wrong about this because then I can I learn something new. The way I understand update mechanisms is that there are three ways things get updated in one's phone: the first is by Google and traditionally Google has only updated parts of the operating system that have to do with Google such as the Play Store or the Google framework etc. and these are considered minor patches to the OS. I have never heard or seen that Google would modify the /system partition as that would defy the entire notion of factory reset. The second is through Samsung. unless you live in certain countries where Samsung sells you a phone unlocked and unattached to a mobile operator the update you get from Samsung is limited to Samsung applications and security patches. Finally, in the United States and countries where phones are sold by cell phone operators the OS update is delegated to the phone companies such as AT&T and t-mobile. that's how you get an update for example from kit Kat to lollipop in the us. there is no documented mechanism that shows how Google can update the OS on a phone sold to you by a phone company. but if you find non anecdotal evidence to the contrary, I would be glad to stand corrected.
najoor said:
I'm sorry, I am not questioning your judgment about this and as always I would like to be wrong about this because then I can I learn something new. The way I understand update mechanisms is that there are three ways things get updated in one's phone: the first is by Google and traditionally Google has only updated parts of the operating system that have to do with Google such as the Play Store or the Google framework etc. and these are considered minor patches to the OS. I have never heard or seen that Google would modify the /system partition as that would defy the entire notion of factory reset. The second is through Samsung. unless you live in certain countries where Samsung sells you a phone unlocked and unattached to a mobile operator the update you get from Samsung is limited to Samsung applications and security patches. Finally, in the United States and countries where phones are sold by cell phone operators the OS update is delegated to the phone companies such as AT&T and t-mobile. that's how you get an update for example from kit Kat to lollipop in the us. there is no documented mechanism that shows how Google can update the OS on a phone sold to you by a phone company. but if you find non anecdotal evidence to the contrary, I would be glad to stand corrected.
Click to expand...
Click to collapse
I mean, I'm not stating that it was Google who pushed this update, it is an AT&T ROM after all. The reality of my situation is that the phone was doing an initial startup and the very first thing that happened was it launched into the initial setup. Once it got to the screen that asked me for my Google login to re-install all the apps that were linked to my account, that was the last time I had any input over the matter. It had to be during this time that the 5.0 update was downloaded/installed as well because this process took about an hour while it downloaded everything. Unfortunately it gives no information about whats going on whatsoever except for showing a splash screen that you can't escape from as it continued to download everything. Once it finished, I was at 5.0. I never once saw the phone operating or a home screen on anything that wasn't 5.0. So it very well could have been that AT&T pushed the OTA update during this process. I just had zero control over what was happening and was never prompted for an OTA update. I just entered my Google credentials, it went to the splash screen, and when it finished it spit me out to the home screen at 5.0.
changoland said:
I mean, I'm not stating that it was Google who pushed this update, it is an AT&T ROM after all. The reality of my situation is that the phone was doing an initial startup and the very first thing that happened was it launched into the initial setup. Once it got to the screen that asked me for my Google login to re-install all the apps that were linked to my account, that was the last time I had any input over the matter. It had to be during this time that the 5.0 update was downloaded/installed as well because this process took about an hour while it downloaded everything. Unfortunately it gives no information about whats going on whatsoever except for showing a splash screen that you can't escape from as it continued to download everything. Once it finished, I was at 5.0. I never once saw the phone operating or a home screen on anything that wasn't 5.0. So it very well could have been that AT&T pushed the OTA update during this process. I just had zero control over what was happening and was never prompted for an OTA update. I just entered my Google credentials, it went to the splash screen, and when it finished it spit me out to the home screen at 5.0.
Click to expand...
Click to collapse
My S5 looks for system updates on the initial setup each time. It probably upgraded to the new OS as your were doing your initial setup of the device.
That's correct it does look for updates on initial setup. I have made it a good practice not to connect to Internet during the initial setup. This will keep it from looking or installing any updates. Updates will not push unless your connected to Internet ( unless it's been days and you keep denying them ).
This is the procedure I follow each time I buy a new phone:
1- Take the sim card out and turn the phone on. If the phone co-operates go to step 3.
2- Put the sim card back in and turn the phone on.
3- During the initial setup decline to connect to WiFi if the phone accepts that.
4- Immediately after the set up is complete, go to Settings -> Security -> security policy updates (or something like that) and turn automatic updates off AND set your preferred networks to WiFi only.
5- go to Settings -> about device -> software update, AND IF THERE IS AN OPTION PRESENT, disable automatic updates.
6- Root the phone if possible. If not move to step 8.
7- After obtaining root, disable the update related apks. They are typically called: LocalFota.apk, FotaClient.apk, SamsungApps.apk, SPDClient.apk, SyncmlD.apk, and wssyncmlnps.apk, or variations of these names. They are all under either /system/app or /system/priv-app.
8- It is now (relatively) safe to connect to the internet.
9- The first time you log in to playstore, quickly go to its settings and disable automatic update.
najoor said:
This is the procedure I follow each time I buy a new phone:
1- Take the sim card out and turn the phone on. If the phone co-operates go to step 3.
2- Put the sim card back in and turn the phone on.
3- During the initial setup decline to connect to WiFi if the phone accepts that.
4- Immediately after the set up is complete, go to Settings -> Security -> security policy updates (or something like that) and turn automatic updates off AND set your preferred networks to WiFi only.
5- go to Settings -> about device -> software update, AND IF THERE IS AN OPTION PRESENT, disable automatic updates.
6- Root the phone if possible. If not move to step 8.
7- After obtaining root, disable the update related apks. They are typically called: LocalFota.apk, FotaClient.apk, SamsungApps.apk, SPDClient.apk, SyncmlD.apk, and wssyncmlnps.apk, or variations of these names. They are all under either /system/app or /system/priv-app.
8- It is now (relatively) safe to connect to the internet.
9- The first time you log in to playstore, quickly go to its settings and disable automatic update.
Click to expand...
Click to collapse
Those are good steps, one side note that i do is i don't connect to Internet until after i sign into Google play and set the update to " do not update ". I also hardly ever connect to the Internet anyhow since my phones data is faster than my slow a$$ Internet. Ha
dirtydodge said:
Those are good steps, one side note that i do is i don't connect to Internet until after i sign into Google play and set the update to " do not update ". I also hardly ever connect to the Internet anyhow since my phones data is faster than my slow a$$ Internet. Ha
Click to expand...
Click to collapse
Yeah, but somehow that never worked for me. Play store doesn't let me log in until I connect to the internet and before logging in I cannot change the settings.
najoor said:
Yeah, but somehow that never worked for me. Play store doesn't let me log in until I connect to the internet and before logging in I cannot change the settings.
Click to expand...
Click to collapse
If you open the play store and log in that way it normally won't, but if you go to settings, accounts, and add your Google account that way, let the phone set about 5 min while it sets up then you should be able to log in.
changoland said:
That sucks, I assumed at first that it came out of the box at 5.0, but it must have updated to 5.0 when it restored all my apps through Google during initial setup...
Click to expand...
Click to collapse
What makes you think it didn't come from at&t with 5.0 already installed? I had to have my phone replaced recently and the new one definitely had 5.0 pre-installed.
I just received one, 5.0 out of the box also.
Ok, so I'm not the only one who received a 5.0 out of the box. too bad AT&T are such pieces of s***
Yeah, I entered this thread with the intention of posting that it was to my understanding that unless you find some old stock somewhere, all new AT&T Galaxy S5s are coming with 5.0 pre-installed.
If the OP had taken an OTA while setting up his phone I'm sure he would have noticed the reboot to recovery and the little Android dude with the blue progress bar under him as his phone updated. OTA updates don't silently install.
The days of walking out of the store with a brand new S5 and rooting it right away have gone away until someone finds a new exploit that will work on the stock 5.0.
I'm looking for a used S5 to use on Straight Talk. I want to root it and use the mobile hotspot feature. Is their a particular build number or kernel I should be looking for? I want to have 5.0 also. Maybe a ROM like Sixperience
THANKS
Downgrade and root?
I had the same issue, replaced my broken S5 and the new one came with 5.0 stock.
Would it possible to downgrade, to 4.4.2 KitKat, root via Towelroot, and then upgrade again? Would be tedious, but I am sick of AT&T's bull****. It's a moral victory as much as just looking for more ease-of-use.
bigben7310 said:
I had the same issue, replaced my broken S5 and the new one came with 5.0 stock.
Would it possible to downgrade, to 4.4.2 KitKat, root via Towelroot, and then upgrade again? Would be tedious, but I am sick of AT&T's bull****. It's a moral victory as much as just looking for more ease-of-use.
Click to expand...
Click to collapse
Not possible as of now
Sent from my SAMSUNG-SM-G900A using Tapatalk
We have a family plan with T-mobile, and three of the four phones are the HTC One m-9. Mine is a Galaxy note 5.
My son's HTC phone received the latest OTA update three days ago. The one dated 9/27/16 with version number 3.39.531.21. It is available here: http://www.htc.com/us/support/htc-one-m9-t-mobile/news/
I have never rooted it, it being my son's phone, but I've rooted my own phones in the past.
We plugged it in and started the update and went to bed.
In the morning on the way to school, my son showed me the initial encryption screen. It would not take his password. He and I tried several times. He has allways had the same password and has never changed it - he is required to not change it without telling us or he knows he will lose his phone.
At a loss, I booted into the stock recovery and wiped the cache, and then did a system reset.
Now the Google "Verify your account" screen is impassable. It does not remember the Google account that we have always used with this phone, and so now there is no way to actually use the phone.
I also tried reinstalling the 3.39.531.21 update using the link above. The rom updated seemingly perfectly, but I still have the same security block.
I will be calling T-mobile to see if i get anywhere, but I also thought I would ask here since I doubt they will have much to offer me. This is not a stolen or transferred phone - we bought it direct from the T Mobile website brand new and the receipt for this phone is still in my email. My son's google account is the only account that has ever been on it. Is there any way to get around the google theft verification?
I'm getting nagged to update my software even though I've disabled updates for the Motorola updates service, and disabled automatic updates in developer options. I'm currently running stock Oreo, and have been getting these every 24 hours or so, sometimes more.
I'm fine with taking the security updates, but I really don't want to upgrade to Pie. So much so that I exchanged the first X4 I had just so I could stay on the older update with a locked bootloader. My main concern is that I accidentally updated already, because they eventually take away the option to be reminded later instead. At this point I think I know how to avoid consenting to the update, but it would be nice if this annoyance was gone for good.
nguinn said:
I'm getting nagged to update my software even though I've disabled updates for the Motorola updates service, and disabled automatic updates in developer options. I'm currently running stock Oreo, and have been getting these every 24 hours or so, sometimes more.
I'm fine with taking the security updates, but I really don't want to upgrade to Pie. So much so that I exchanged the first X4 I had just so I could stay on the older update with a locked bootloader. My main concern is that I accidentally updated already, because they eventually take away the option to be reminded later instead. At this point I think I know how to avoid consenting to the update, but it would be nice if this annoyance was gone for good.
Click to expand...
Click to collapse
I had the exact same problem with the three moto x4 Amazon Prime versions. I contacted Amazon and Motorola - both told me there was no way to stop the update notices. I even explored app lockers hoping to find one that would let me lock the update notice app - no luck.
I finally gave up, purchased three moto x4 Android one versions (they are rootable) on sale at Best Buy, rooted them, then disabled the Motorola update service. No more update notices.
nogods said:
I had the exact same problem with the three moto x4 Amazon Prime versions. I contacted Amazon and Motorola - both told me there was no way to stop the update notices. I even explored app lockers hoping to find one that would let me lock the update notice app - no luck.
I finally gave up, purchased three moto x4 Android one versions (they are rootable) on sale at Best Buy, rooted them, then disabled the Motorola update service. No more update notices.
Click to expand...
Click to collapse
I see, I was afraid of that. I should have mentioned that I have the Android one version, but I was hoping not to have to root it. I play Pokemon GO sometimes, and it doesn't like it when your device is rooted, even using the method that's supposed to hide it.
Has anyone had any luck breaking OTA updates, possibly by flashing a slightly modified version of stock software? I was hoping to stay stock because that's usually best for the camera, but Gcam should get around that, right?
nguinn, just use magisk. i play PoGo also. use the X4 to GPS spoof for regional exclusives. works great. reddit.com/r/pokemongospoofing has a great tutorial on how to root your phone to make pokemon go not be able to see it.