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?
Hi guys. I am stuck at an impasse here and I know someone here will be able to help.
My wife and I just bought two Samsung Galaxy 2 Epics (refurbished) from the retailer Glyde. I purchased from them because they are partnered with my new carrier, Ting.
My phone activated and ported my number with no issues. Everything works perfectly.
Her phone appeared to activate and then rebooted. It will not go past the Sprint 4G animated opening. I have rebooted, wiped cache, and done factory reset. Still ... 4G logo animation appears and the screen either goes black (appears to shut down) or it just stays on the 4G logo without moving on and then a few minutes later goes black. The phone worked fine before we tried to activate it. It logged in her gmail and connected to wifi.
I am able to get to recovery mode. I was probably going to root and cyanogenmod mine. In your opinion, would this type of action possibly correct the problem with her phone? Is it possible to root and flash the original stock rom in a situation like this? Would that even work seeing that factory reset did no good?
I have contacted Glyde and am waiting - they may or may not replace. If they do replace that is a 2-3 week turn-around. I would rather work some magic here, if possible.
Thoughts and help are appreciated!
Brian
You might have to Odin a stock rom most likely
? Powered By My Moga Pro ?
9/10 Times if you can Odin it, you can fix it. BUT, restoring to stock via Odin will break your flash.
Chances are your flash is already cracked up a little.
A simple cricket nv gen google search combined with Odin, drivers, and DFS Tool. You'll be able to get it back up and running smoothly.
And if your device was on a stock rooted ROM, and you have a custom recovery, then flash a 4.1.2 Custom touchwiz ROM. That way, no programming will be lost.
If you decide to flash an AOSP/AOKP ROM like Cyanogen you could possibly break your flash.
2 cents.
fixed
Would you guys believe it was the battery? It was. I swapped batteries and the other phone started doing the same thing. Battery replaced and problem solved. I guess I panicked, but it sure seemed like a software issue. Thanks for the advice.
So I have traditionally been a rom junkie, trying new ones each week (both aosp and tw), however I recently became more entrenched in touchwiz due to the battery savings. I was using Ditto Note 3 when I noticed that my GPS appeared to never find a lock, despite multiple applications such as gps toolbox and also leaving it to load outside for long periods.
I found another thread on the GS3 which described accessing service mode using the code in dialer '#*197328640#' and going into UMTS/COMMON/NV REBUILD to reset nv data. This let me access the menu on tw roms, however everytime I got to the NV REBUILD screen, it always said 'not support in custom binary' with both rooted and unrooted stock.
I have since unrooted my phone in a last ditch attempt to avoid returning it for repair as I am still on 4.1.2 bootloader and have a warranty for another 7 months- I don't want them to update my software to add knox, which I know will occur if I do this. Even on unrooted stock 4.1.2 after verifying that my download bootup screen shows no custom binary, official software and status official, along with a 'normal' status in phone settings, it is still giving me that same error in service mode.
Does anyone have any ideas? I'm seriously lost on this, and I need gps for work. Any tips would be greatly appreciated.
Help!
I have the exact same problem right now. Did you manage to fix this?
Nope- I ultimately handed it in for repair and got myself a knox'd replacement. That being said, the warranty would be up now regardless so it didn't matter. It might have been a hardware fault as I've flashed about 20 different roms since then and had no issues locking gps. Good luck!
Quick story: I rooted my note 2 about a year ago. Ran Paranoid Android for a long time. got it in my head I wanted to revert back to stock. So I did, successfully. I then did all the updates, including the dreaded knox firmware. I then went back to PA, but with knox on the phone I was never able to get root access. I did get PA to stick somehow, but for the last 2 months i've been without my LTE. So I decided to revert again, successfully. Because I'm a glutton for punishment I allowed the stock update to kitkat 4.3, which soft bricked my phone. This was after it had been working on 4.1 for a half a day. A really nice guy in this thread showed me how to unbrick my phone and get it back to the bootloader. From there I was able to run the revert to stock again and my phone is again happily running stock 4.1.
All of that is leading to this, the actual question. My phone is constantly hanging when the OS asks if I want to upgrade. I've tried it a couple more times at this point to see if it was just a fluke that the update didn't take. Is soft bricks the phone every time...how do I get the phone updated to 4.3 so it stops asking?? At this point I am stock. I also tried running the auto root but it runs into knox (i think, something goes wrong) and wont take
Dont care what I have to do at this point, the knox counter is already tripped. Although it doesn't show up after running the revert to stock rom.
Our phone slowly starts freezing on touch input on the screen until it no longer recognizes input and stays at the lock screen. Home key and menu/back arrow remain functional, but we have a pin lock. Wiping the android db cache in the boot menu restored it to normal for a few weeks, then it began the gradual descent into frozen territory. Restoring the firmware via kies worked for a month. This was bought as unopened replacement from swappa. This started happening after we installed the OTA update around November. It was dropped in water on Thanksgiving, and we had the micro USB board swapped out for repair, however we didn't notice any freezing until after the New Year.
Is this a common problem with the OTA update Tmo sent out? I don't think it is a residual problem with water damage- would a digitizer problem be fixed with the wiping/kies firmware update? Would I be able to flash the google play edition rom on this instead? Thanks for any help
It's most likely due to the water damage, being that you had a board replaced tells me that there was damage and now something else is failing.
You probably need a replacement phone.
Pp.
After flashing the Kies based stock rom again, it only un-froze after wiping data and cache. After that, I just decided to go ahead and try stock GPE 5.0 on it from muniz_ri. That flashed and it was working again last night. I don't believe it is the digitizer as flashing different software wouldn't restore it back to working order if it was a hardware defect, I would imagine.