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 folks,
I rooted my GS3 right after I got it and everything has been functioning fine. I actually like the stock ROM so I have stuck with it and just removed the bloat. Recently an OTA update was released and I followed an article on putting my updater back to stock to receive the OTA update. I tried updating but it was unable to complete. Now when I go into software updates there is an option that says "continue update" that is grayed out. Is there a workaround to this or do I need to flash back to stock, receive the new update and reroot? If that's the case a link to a walk through would be appreciated. Thanks
anyone?
I was able to get to 4.1 successfully with kies this morning
After browsing the internet all day yesterday I never did see an actual fix for this issue for this specific model. I did see a lot of random ones for different carriers which would probably work. But not for Sprint specifically.
Problem? My Sprint Galaxy Tab 3 7" failed at 27% whenever I attempted to update it.
Issue: The Tab was Rooted by my brother - who then Un-Rooted and returned it back to Factory before giving it to me. Then failed to mention he had rooted the thing to begin with.
Fix: Re-Flash using Odin and stock 4.2 image.
So I tried getting Kies installed and working. Tab would NEVER connect no matter what I did. I tried installing the USB drivers again (though the computer recognized the damn thing), reinstalling Kies, trying to put Kies into Compatibility mode (since I'm on Windows 8.1)
After ALL that I finally called my brother who gave it to me as a gift. Found out the thing may or may not have been Rooted. But he thought he had reverted it back to stock and un-rooted it.
So back to searching on the internet. Finally found this article: http://theunlockr.com/2014/03/21/unroot-samsung-galaxy-tab-3-7-0-sprint/ which suggested I try re-flashing using Odin to get rid of Root on the device.
I followed the steps in the article (Tip: Do a search on Google for the correct image zip for your model tablet and download it from androidhostfiles) Example for my specific model T217SVPUANB8: http://www.androidfilehost.com/?fid=23329332407579787
Was able to restore it back to "true stock" and was able to update to KitKat. Kies started working finally. And all was well with the world again.
Oh, and I uninstalled Kies immediately after I was done with that POS software. :silly:
Hopefully this will help the I dunno the two other people that still have one of these that they received for free from Sprint.
looking for some suggestions as to what I can to to correct these issues. I have a 210R that I screwed up probably flashed something I should not have... to restore I went to sam mobil and downloaded the latest firmware ( T210RUEU0COB1), installed using Oden and restored the Tab. since I have done this (and yes I redownloaded the firmware and reinstalled to make sure it was a good file and installation) the tab now will boot up fine, but will come up with the error messages Process com.androis.systemui has stopped and often com.sec.android.flashbarservice has stopped as well clicking ok will sometimes let me continue, other times will simply reboot. If it lets me continue whatever app I am using will quickly stop as well and the tab reboots. in addition to this the WiFi barely recieves any signal unless I am almost on top of the router. it is currently stock. Any suggestions or help will be greatly appreciated.
Having the same problems minus wifi issues
jdsatyr said:
looking for some suggestions as to what I can to to correct these issues. I have a 210R that I screwed up probably flashed something I should not have... to restore I went to sam mobil and downloaded the latest firmware ( T210RUEU0COB1), installed using Oden and restored the Tab. since I have done this (and yes I redownloaded the firmware and reinstalled to make sure it was a good file and installation) the tab now will boot up fine, but will come up with the error messages Process com.androis.systemui has stopped and often com.sec.android.flashbarservice has stopped as well clicking ok will sometimes let me continue, other times will simply reboot. If it lets me continue whatever app I am using will quickly stop as well and the tab reboots. in addition to this the WiFi barely recieves any signal unless I am almost on top of the router. it is currently stock. Any suggestions or help will be greatly appreciated.
Click to expand...
Click to collapse
Dude my tablet is in the same state I use. The many reboots. All apps/process stopping for no reason. Funny thing is this started happening to me after I received an OTA update for 4.4.2 and flashed it. So basically the official update released by samsung messed up my phone. Somebody please respond with suggestions/solutions.
Sigh.... guess I'll just use it as a paperweight ..
Good Afternoon everyone!
A while back I bought a sprint s8 plus and flashed tmobile software via Odin. All went well except that my phone keeps prompting for an update, however every time that i go through with the update it does the whole process then returns to the homescreen to then prompt for the same update. I have tried updating about 10 times to only have the same problem, any suggestions? I flashed G955USQU1AQD9_Recovery_TMB
Thank you in advance for any help!