I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
robertlewisca said:
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
Click to expand...
Click to collapse
I was having the same exact problem. I even changed phones thru warranty. The new phone did the same thing. New SIM card didn't help. I had a guy at tech support to push the update to me.
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
IDK, co-worker with a Skyrocket has had the same issue, but he doesn't care about the update, so he hasn't bothered to get it resolved.
If I didn't have a red GS3, I could goof around and tell you that is what the problem is...
Actually, if it were me having the issue, I'd walk into AT&T and have their guys mess around with it. No telling why some have more issues than others.
robertlewisca said:
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
Click to expand...
Click to collapse
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Not really a solution but you could install this http://forum.xda-developers.com/showthread.php?t=1902178 to be fully stock LH9 with Root. Or use the OTA zip from here http://forum.xda-developers.com/showthread.php?t=1896773.
aboveusonlysky said:
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Click to expand...
Click to collapse
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
78c10 said:
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
Click to expand...
Click to collapse
You mention in your signature that your phone is rooted. So, did you update OTA then root, or did you update after rooting through some other method? The challenge some of us are having is that we are not rooted, and cannot update OTA because of the 'server error' it gives us everytime we try.
Problem Solved - for me at least
Well, the problem is solved for me, and I thought I would share what I found out here in hopes it helps someone else.
First, I had the phone replaced under warranty. It appears to be a brand new phone. When I received the new phone, I started it up, went through the normal startup stuff - entered my Google account information, it backed up my info and settings. Before I loaded any apps, I went straight to the update screen, and tried to check for an update. I again got the 'communication failed' error. Bummer.
So, then, I did a factory reset on the new phone, but this time instead of entering the initial Google account info on the startup screens, I skipped through all of the initial screens, got to the home screen, then went straight to the update screen - and this time it worked! So, it must be something to do with the initial screens, and entering Google account information that caused the problem.
Then, I got to thinking - perhaps this might work on my old phone too. Since I just got the warranty phone today, I still had my old phone (which needs to be sent back). So, I did a factory reset on it, skipped all of the initial screens where it asks for Google account information, and it still didn't work on the old phone. So, I'm not sure what the original issue was.
By the way, after the update installed on the new phone, and I went through and entered all of the Google account settings, and then checked for the update again, and there was no error.
So, perhaps this might be helpful for others?
Hey everyone,
So two night ago I received a notification on my GS3 saying a new update was out.
When I tried installing the update it rebooted into recovery and failed at 24%....weird. I was running Rogers stock rom and recovery at the time so this shouldn't have happened, and I would like to know why for future reference.
I also tried updating via samsung kies. But when I tried this, it said my device wasn't compatible to update via kies????
So I ended up download the LK4 update off sammobile website and installed it using odin.
Anyways, I now have the new update installed. I've noticed two weird things:
1. When I go to about phone in settings and go into software update, it shows a screen "checking for software updates..." and doesn't go away unless I press back or home button. Why can't I search for new updates????
2. My google now voice isn't working. It recognizes what I say to it but when it gives the flashcard response, it doesn't talk back like it normally does. I have it set to English US, and yes my media volume is up at full volume.
Anyways I'm a little frustrated at this point. I can't figure out how to fix these problems so any help would be greatly appreciated. Thanks
I've been working off and on for a week on this and I'm guessing I'm out of luck but figured I'd ask just in case I missed something on here.
I've been attempting to resurrect my father's GNex. He had it working fine -- stock 4.2.2 via OTA updates - it's never even been unlocked -- and then suddenly it gets stuck in a bootloop. He tried resetting it back to factory settings but it continued the loop -- would get as far as the language selection screen and then would reboot.
I attempted to unlock/reflash using the toolkit and it would get stuck on flashing the CDMA radio -- will hang for hours if I let it. I've tried the current 4.2.2 build, the original 4.0.4 using the GalazyNexusRestore utility, and everything in between. I've tried flashing the radios via CWM as well.
Of course I only attempted this myself (I've been rooting and installing ROMs since the G1) because the warranty ran out in August. Is there anything else I can try before giving him the bad news?
first of all have you tried odin? (basically its samsungs flashing tool)
second of all is a verizon gnex or sprint? (both are cdma)
for verizon try this- http://www.galaxynexusforum.com/forum/rescue-squad/4707-how-return-stock-using-odin-vzw-lte-only.html
for sprint try googling for "sprint galaxy nexus stock odin files" (mainly all you need are the correct files for sprint and the guide in the verizon post should work)
Finally got around to trying Odin. Just gave it a go (I've got a verizon phone) and it failed on radio.img.
I assume that there's nothing else that can be done?
Heya people.
I have a weird issue.
First some history.
I bought this phone years ago as a backup and soon after I decided I did not like it and got another phone. Meanwhile I fiddled with custom roms. This was back in 2012 probably so im pretty sure the rom that is on the phone now is Cyanogenmod unofficial android 4.0.
Phone boots fine but is quite unstable. random reboots etc when using it to its fullest.
I litterally threw it in a box, and forgot about it. until my mom called me needing an emergency phone. I remember I had it and offered it. Saying it could be there in about a day or 2. She needs a phone for a couple off weeks till her current phone gets replaced by Huawei since it broke. She specificly needed a simlock free phone. Mine is unlocked so that would have been great.
So I read up about Odin and how you are supposed to reflash to stock firmware. Downloaded the stock firmware from Samfirmwares. Dutch firmware. I downloaded 2 versions since there is a vanilla one and a vodafone branded one.(my phone is the vodafone branded one so I tried that one first)
First I used the newest Odin version and it didnt work. Got stuck on setup connection for about 5 minutes and then timesout with a fail.....
Ok so I went back to browsing and found that using a older version of Odin might work. Been there done that. tried 4-5 different lower numbered Odin versions. All the same issues. Switched USB ports multiple times and also doesnt work.
I am currently at a loss.
PS I also tried the Samsung Kies method.. Initialize firmware and upgrade. type model number(succes) type serial number(succes) then it tells me my device is unsupported for this method.
Here's the story. I purchased a factory refurb'd Tab Pro 10.1 (SM-T520NZKAXAR) on Woot a few weeks back. I live in Canada, but it is a USA tablet, if that matters. It came with a 90-day Samsung warranty. As soon as I got it, I started looking at custom ROMs. I have experience with custom ROMs on my HTC One m8 (and old m7), but not with any Samsung devices. I wish I had kept it stock for a few weeks first to check it out, but here we are.
I created a nandroid backup of the stock firmware, however I quickly deleted it during a wipe when flashing my first custom ROM, which was GraveD's v3.0. It seemed to go OK, but then it would start to freeze up and reboot on it's own. This seemed to happen mostly under load, and especially when trying to install apps from the Play store. I tried going back to the stock kernel, thinking that could be the problem. It stopped the crashing, but then wifi wouldn't work. So I could choose between having a tablet that crashes all the time, and has difficulty installing apps, or one without wifi. Both were basically useless.
I tried installing another custom ROM, GigaWatts Pro. Again, flashing seemed to go well, and the ROM also seemed to work very nicely for a couple of days. No random reboots, and wifi worked great. I spent a few days downloading all of my apps and getting things set up the way I like, when yesterday something went wrong. Perhaps the tablet lost its root (is that possible?). All of a sudden, apps are crashing all over the place (Unfortunately, [insert app name] has stopped). Titanium backup hangs at "Asking for root...". Installing apps is also difficult again. The tab doesn't reboot on it's own, but Play Services crashes constantly. Whenever I try to get into developer options, the Settings app crashes. I'm not even 100% sure USB debugging is enabled right now, although I'm still able to flash using ODIN.
I tried doing a factory reset and re-installing GigaWatts. Same problems. Tried making sure the root was OK. Same problems. I've tried using twrp 2.8.0.0 as well as 2.7.1.0 with no luck.
Right now, I've downloaded the stock firmware for Canada T520UEUANI1 4.4.2 (although the tab was bought from a USA site). I assume this also installs it's own Kernel. It shows Kernel version:
3.4.39-2776001
[email protected] #1
Mon Sep 15 17:44:40 KST 2014
I'm experiencing the same problems. Google Play Newsstand crashes every 10 minutes or so. Settings is almost useless. Installing apps is problematic.
Can anybody tell me if there's something I'm missing? Anything left to try? Does it sound like a hardware/ROM/kernel problem? If it's hardware, can I still utilize the Samsung warranty after trying to flash custom ROMs? I'm going to try to download another Cellular South stock ROM, but it seems like the problems are persisting regardless of which ROM i have installed, so I think it's something else (kernel or hardware-related).
Any help is GREATLY appreciated. My new tablet is basically useless, and I've run out of ideas.
Try this latest firmware since you mentioned your tablet is the XAR model the firmware should be cellular south (wifi)
http://www.sammobile.com/firmwares/download/39630/T520UEUANK1_T520XARANK1_XAR.zip/
If that doesn't help then it could just be a bad tablet .
(btw when you flashed a custom rom you probably tripped the hardware knox flag and voided any warranty it had, I guess you could play dumb if they ask and say it came like that since it was refurbished, and hope they still repair/replace it)
I just tried the USA cellular south firmware. Still experiencing the exact same issues. I'm completely out of ideas. Does anyone else have any ideas? Otherwise I'm going to have to try warranty service and hope for the best. Is there anything I can do to restore the Knox flag before I send it in?
Also, in download mode the tab is recognizing the system as custom. Is this normal after flashing a stock image?
So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.
k8108 said:
So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.
Click to expand...
Click to collapse
I've tried the Cellular South firmware to no avail. I'll be trying to warranty the tablet now. Fingers crossed!