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?
Issue resolved.
MiasmicTaco said:
This morning my Razr M received the latest OTA update. I was previously rooted with a locked bootloader (I know, bad choice).
I proceeded with the update but my phone massively screwed up: lost wireless, contacts malfunctioned, several apps failed.
I went through all the steps to clear cache, soft reset, hard reset, etc. Ever sense my phone has been stuck on the setup wizard screen stating "Please wait, this may take a few minutes". I left this morning at noon returned home at 7 and it is still on that screen.
Click to expand...
Click to collapse
Try using RSD to restore to the same version (4.4.2). I've gotten that wireless issue before, and I just had to format userdata and reinstall the update to get it working.
just roll back to orginal firmware by using RDS and after that,use OTA update
Hi all. At 4:20 AM PDT (the notification sys 8:20AM for some reason) this morning (June 12) my Note 4 buzzed and woke up and let me know there was a software update available. Any idea what this is?
I didn't install the small security update last month yet, is this just that update trying to be more forceful (the notification will not go away)? Or is it a new update?
Try it, and let us know what it is !
I didn't install last month's security update myself for the fear of losing that slim chance of an unlocked bootloader and root..lol
I haven't received a notification about an update this month..would you happen to have a description of the update?
Well, the notification wasn't going away and I accidentally hit continue and it rebooted and installed whatever it was.
Took it's sweet time installing and then optimizing apps, and as far as I'm aware nothing changed. Same baseband, same kernel, same build number (LMY47X.N910AUCU2DOI3) according to About Device.
Also my phone is starting to show me the same annoying screen that started appearing when the security update came out saying to connect to wifi to download another update (whatever update was installed today, it downloaded itself via mobile, not wifi).
So I am rather confused as to what the 'update' I installed was.
Hello, I'm having a strange issue with March Security Patch update. 3 days ago I received via ota this update, did it and everything was OK. The day after, I rebooted the phone, and sudden it turns black and rebooted by itself looping on coloured little balls before G logo. Another reboot and when it turns on I noticed that it downgraded by itself on February patch security, giving me the March update aviable via ota again.
I reupdated but the day after, once again the same thing. And once again yesterday...and once again today. What have I to do?
hbkekko said:
Hello, I'm having a strange issue with March Security Patch update. 3 days ago I received via ota this update, did it and everything was OK. The day after, I rebooted the phone, and sudden it turns black and rebooted by itself looping on coloured little balls before G logo. Another reboot and when it turns on I noticed that it downgraded by itself on February patch security, giving me the March update aviable via ota again.
I reupdated but the day after, once again the same thing. And once again yesterday...and once again today. What have I to do?
Click to expand...
Click to collapse
Is your bootloader unlocked or any root or anything of that sort? That's a very weird issue. There are reports of the Nexus 6 being downgraded to 7.0 by Google but I'm not sure if it's a software push they are doing to cause that to happen.
You may have to wipe cache and try the update again.
Jammol said:
Is your bootloader unlocked or any root or anything of that sort? That's a very weird issue. There are reports of the Nexus 6 being downgraded to 7.0 by Google but I'm not sure if it's a software push they are doing to cause that to happen.
You may have to wipe cache and try the update again.
Click to expand...
Click to collapse
I tried to wipe cache from settings, storage but didn't work. Yes I've unlocked bootloader but no root. Could this be the problem?
No, shouldn't affect anything just being unlocked. Now if you installed TWRP, that might cause this. I didn't use an OTA to go to the march update so idk if it might be at fault, I was on pure Nexus so chose to flash the factory image and haven't had any issues so far.
Sent from my Pixel XL using Tapatalk
Solved flashing the latest factory image via fastboot
Hey, I have a question.
I've encountered something kind of strange with this device. I've been running Android P with the December 2018 security patch, rooted with Magisk. I've never encountered any problems with it so far except for a few bootloops I've got for deleting some modules in Magisk.
One day I decided to restart my phone because it was kind of laggy and so far so good it was booting. It showed me the Xiaomi logo and then it asked for the pattern to start Android. I entered the pattern and it just got into bootloop. (I've gotten bootloops before but it never got to the point where it shows me the logo and asks for pattern). I don't know what caused the bootloop because lately I haven't been messing with Magisk. However I thought it was a good idea to get into recovery and factory reset it (this has gotten me out of bootloops before so I gave it a try). After the reset it started to bootloop again, I just restarted it and it worked out just fine. I set up my phone, obviously root was gone because of the reset but I realized my phone's gotten updated to the March 2019 security patch. This was quite a surprise because I've been trying to update it and nothing seemed to work. (I tried updating it once by reflashing the original firmware with MiFlash, it was version 10.0.2.0, and before rooting it to install the security updates, they were just failing for no reason because there was no root on the phone).
So do you guys have any idea why my phone got into bootloop out of a sudden? And also why did the update successfully got installed after the factory reset?
Merky_21 said:
Hey, I have a question.
I've encountered something kind of strange with this device. I've been running Android P with the December 2018 security patch, rooted with Magisk. I've never encountered any problems with it so far except for a few bootloops I've got for deleting some modules in Magisk.
One day I decided to restart my phone because it was kind of laggy and so far so good it was booting. It showed me the Xiaomi logo and then it asked for the pattern to start Android. I entered the pattern and it just got into bootloop. (I've gotten bootloops before but it never got to the point where it shows me the logo and asks for pattern). I don't know what caused the bootloop because lately I haven't been messing with Magisk. However I thought it was a good idea to get into recovery and factory reset it (this has gotten me out of bootloops before so I gave it a try). After the reset it started to bootloop again, I just restarted it and it worked out just fine. I set up my phone, obviously root was gone because of the reset but I realized my phone's gotten updated to the March 2019 security patch. This was quite a surprise because I've been trying to update it and nothing seemed to work. (I tried updating it once by reflashing the original firmware with MiFlash, it was version 10.0.2.0, and before rooting it to install the security updates, they were just failing for no reason because there was no root on the phone).
So do you guys have any idea why my phone got into bootloop out of a sudden? And also why did the update successfully got installed after the factory reset?
Click to expand...
Click to collapse
You want help without logs? This is a developers site not Magic kingdom!