Related
WIth five bar and over 1mbps on download test via 3G, I keep getting
"Unable to communicate with ATT server" for Software Update.
Anyone else getting the same message?
I got the same message. I don't know what to do.
Sent from my SAMSUNG-SGH-I897 using XDA App
I wasn't able to. I tried everything and finally was able to put my phone back to the stock settings. Nothing worked. Contacted AT&T and they had no idea. Finally to save myself any trouble I just contacted Amazon, who I bought the phone through, and they are sending me a new phone that should arrive tomorrow.
I spoke with business care yesterday and qouted my/same error message. Whether or not she knew what she was talking about.....who knows, but she said since it was a push I didn't need to "check for update" and that it would happen automatically. Sounded like scripted response to that particular error. I am already running leaked JH7 and noticed significant GPS improvement over stock, JH2 and JH3. Curiosity was getting best of me so I have tried twice since update was available. Very happy with phone other than hesitant "back" button since installing leaked JH7 and removing all bloatware no need to update really until Froyo 2.2
Okay so I have done nothing to my phone other than download apps from the market. I have not rooted or sideloaded or lag fixed or whatever.. wouldn't know how. I also have a brand new sim if that matters or not.
I am getting a message a few minutes after I check for updates that says "Connection Failed, Unable to connect to the AT&T servers". Any idea why this is happening? As I said, I have not done anything to the phone other than download stuff from the market.
I have done this the last 2 days and the same thing happend both times. I don't want to change the date on my phone so i waited the 24 hours. Also as a side note.. I have checked for software updates 2 other times prior to this just for giggles. Once about a week or so after I got the phone and I got a message that said no updates and than again a few weeks ago and it did the same thing it did yesterday and today.. the connection failed message.
I would just wait a couple days then try again. There looks to be nothing you can do on your side. Since the update is rolling out in stages, I bet those who can't connect aren't "allowed" to update yet.
Yesterday the update completely bricked my phone. I exchanged the phone last night and again today as both I got had alot of issues (GPS Test finds 0 satallites regardless of where I am - my first phone that bricked worked great, Can't even connect to Android Market on my new phone...).
Since last night I couldn't connect either. I just spoke with AT&T, they told me to exchange my phone against and offered to give me an $85 credit to my account for the inconvenience.
If my next phone doesn't work like my first, I might be done with the Captivate... And i love this phone.
I have the same message when I try to check for the update. When did you all buy your Captivate? I bought mine on September 3rd. I wonder if they roll the update out to the folks that bough the phone earlier this year and block the newer users.
I bought my captivate the day it came out.
I got mine 3 days before it came out and I cannot connect
I think it might be to excessive server load on the part of AT&T. It might just throw out your request if there are too many people downloading
My phone has NEVER been able to connect. Bought it launch day and while playing with it I tried to see what that function did. It didn't connect but I figured everything was fine and it would work when it needed to...until this update came out and it still wouldn't connect.
Went to the AT&T store - their solution was to replace my SIM card because that MUST be the problem. No dice. They threw up their hands and handed me the phone number to get a warranty exchange.
It was pretty funny watching them try to navigate the menus. I can't believe they sell the product and don't know a thing about it.
Much like the poster above me, when I got mine (mid-August), I attempted to update just to make sure I would have the latest software at that time. It failed to connect and when I tried 24hrs later, still couldn't. So I just gave up unworried. I haven't gotten the update yet and will give it thru tomorrow before I try again. For what it's worth, the gps has always worked fine for me.
I get the same things, no root, nothing. I have a feeling that it just hasnt been released to us yet. I could be wrong and if so its gonna really suck. I bought mine 3 weeks ago from Amazon.
Something that would confirm to me that its just that it hasnt been released is if someone who got this message magically starts working the next day, whatever. Anyone?
I'm not really sure what to believe.. Seems like many others can at least see the update from the software update menu -
some have brought their phones into at&t and gotten a new phone that does get the update manually as well.. I am well past the 30 day return and like a lot of us, have flashed other roms, etc- But this doesn't seem to be a problem with some as they are still able to get the OTA update..
I assume we just wait for the next few weeks as they push the update to everyone- but who wants to wait that long??
I understand 100% about not waiting. I keep bumping my calendar forward and trying again....Im up to some where in first part of October already.
Mine always comes up with two arrows in the upper left corner. Once, before it failed to communicate it in the top of the screen in the center it came up with a white circle with arrows inside it. In a few seconds it gave the failed to communicate.
Yea, I agree with whom said that it is prob a server rejection on the matter.. guess we will have to wait. T_T
PersonOfKnownOrigin said:
My phone has NEVER been able to connect. Bought it launch day and while playing with it I tried to see what that function did. It didn't connect but I figured everything was fine and it would work when it needed to...until this update came out and it still wouldn't connect.
Went to the AT&T store - their solution was to replace my SIM card because that MUST be the problem. No dice. They threw up their hands and handed me the phone number to get a warranty exchange.
It was pretty funny watching them try to navigate the menus. I can't believe they sell the product and don't know a thing about it.
Click to expand...
Click to collapse
Except for the ATT store thing, I've had the exact same experience. Never been able to connect, and my update clock (to ping the server) gets reset to 24h. Even though it couldn't communicate in the first place. This happened before and after root. Never thought to go to the ATT store since I got the phone online.
I wonder if it has to do with locale. A lot of the people posting "no problem" or that they got updates are not in the coastal cities with a lot of ATT server load (e.g., SF and NYC). I'm in NYC. Could that be it?
vijtable said:
I wonder if it has to do with locale. A lot of the people posting "no problem" or that they got updates are not in the coastal cities with a lot of ATT server load (e.g., SF and NYC). I'm in NYC. Could that be it?
Click to expand...
Click to collapse
I'm in Wichita, KS, by no stretch of imagination could this place be a congested area. I have had the same issue since day 1.
vijtable said:
Except for the ATT store thing, I've had the exact same experience. Never been able to connect, and my update clock (to ping the server) gets reset to 24h. Even though it couldn't communicate in the first place. This happened before and after root. Never thought to go to the ATT store since I got the phone online.
I wonder if it has to do with locale. A lot of the people posting "no problem" or that they got updates are not in the coastal cities with a lot of ATT server load (e.g., SF and NYC). I'm in NYC. Could that be it?
Click to expand...
Click to collapse
I'm also in NYC, but my SIM is still on my iphone 3GS contract. (got the phone from ebay).
and my calender is already up to...Jan 1 2011.
I give up.
Downloads to 100%, I tell it to proceed, phone reboots, returns to the launcher and I get "The update was not completed. No update is applied to your phone."
That is followed with "Connection failed. Unable to connect to AT&T server."
Now when I try to even enter the software update screen I get "No Firmware" and nothing at all happens.
I've been through this twice now, each time backup up the entire phone using ROM manager before I try to update and after it fails, restore to before the failed update attempt. Sick of trying to get the update and sick of the GPS not working.
Update FAIL. Reading the dozens of stories of all the other people with problems it makes me not even want to try any more. I don't understand how with some people it works and others it fails with what seems to be no rhyme or reason.
Maybe I should backup, completely wipe the phone then try the update. But again, I've read of people trying that with no luck. I just don't get it.
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.
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
I bought two Nexus 6's from Amazon (USA) because they are supper good deals right now at $349. I picked up two identical devices, 32GB Cloud White - they are US models XT1103, they were sealed the same way as my first Nexus 6 from Google Play Store a year ago. But, when I powered them one, one updated from 5.1 to 5.1.1 and after that right to 6.0 while the other one will not, no matter what get any OTA. I tried clearing device cashe memory, I tried clicking "update device", I tried hard reset, I tried clearing Google Framework Services and force stopping it. Nothing works. I don't want to flash manually, I want the OTA. Can someone tell me why this is happening and what I can do to fix it? Thank you
Each device receives it's update whenever Google sends it. Simple as that
bigstunta101 said:
Each device receives it's update whenever Google sends it. Simple as that
Click to expand...
Click to collapse
Did you bother reading my whole post? I'm not worried about 6.0, I'm worried why I'm not getting OTA download of months old 5.1.1. out of the box?
Happening to many people... Google seems to be loosing that which only they had on Android space... reliable updating.
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?