Develop Bugs

[WARNING] Google Music and Root [MEGA UPDATE--FIXED]

If you have root, then be careful. If you authorize 10 devices (different ROMs) to your Google Account, then you can't add any more. It used to be as simple as deauthorizing devices every time you reach you limit. As of now, you can only deauthorize 4 device PER YEAR. Be careful...I just had to reupload all my music to a different account because of this.
MEGA SUPER ULTRA EDIT: Google appears to have fixed the issue. Both Adrynalyne and I can now deauthorize devices. It still says the 4 device restriction applies, but seems to be fixed. YAY GOOGLE!

Good thing I just deauthorized all but two devices! This blows
Sent from my Galaxy Nexus using xda premium

when did this start happening? I unauthorized devices all the time on my account.

I called and they said it happened within the last 60 days. They couldn't do anything, but passed it onto Level 2 Tech Support and will email me if they can manually deauthorize my devices.

Got phones?
...of the people, by the people, for the people...

How does Google determine if your device is the same or not? Something in build.prop? If when flashing between ROMs we keep this value the same, your device would always appear to be the same. Problem solved.
Sent from my Galaxy Nexus

snkrhead2323 said:
Good thing I just deauthorized all but two devices! This blows
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Me too! I did just check to make sure it wouldn't let me deauthorize anymore, and Amphibliam is correct. Quite a bummer. Do let us know if you are able to manually deauth any devices or if any other workarounds are found.

ragnarokx said:
How does Google determine if your device is the same or not? Something in build.prop? If when flashing between ROMs we keep this value the same, your device would always appear to be the same. Problem solved.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I think it has to do with how the app authenticates with your Google account. Each time you click "allow" on the prompt to allow the Music app access to your account counts as an activation.

I'm stealing this info thanks
Sent from my PG86100 using xda premium

Def. Need to find a way around this. I'm maxed out on deauthorizations and I'm at 8 devices.
Sent from my Galaxy Nexus using xda premium

codesplice said:
I think it has to do with how the app authenticates with your Google account. Each time you click "allow" on the prompt to allow the Music app access to your account counts as an activation.
Click to expand...
Click to collapse
Last time I changed ROMs and restored Google Music with data via MyBackup, it didn't ask me to authorize - it was already authorized. Potential work around?

Possibly. Doesn't help me at this point. My tenth device was reached when I upgraded to build 36. I forgot to flash gapps, so it killed all my google accounts. I tried restoring data from the Music app on my Inc2, but no dice. My guess is once this s**t really hits the fan, people are gonna find a fix. If this happens again with no workaround, my fix is called Amazon MP3.

http://support.google.com/googleplay/bin/answer.py?hl=en&answer=1230356
Sent from my Galaxy Nexus using xda premium

"Please note that you can only revoke access to four devices per year."

They can't provide an AOSP supported device and then limit Google services to it and not expect an uproar.
Seems to me a simple data wipe would do the same thing.

Honestly, the only reasons why this isn't widespread is because people just haven't flashed enough ROMs yet. This won't just affect the Nexus, but ANY rooted Android device that flashes 15 or more ROMs in a year. Which is like 99% of the rooted population. My guess is that within 1-2 months, this will be all over the internet. I was just unlucky enough to be one of the first. But this really is absurd. What is the reasoning behind limiting the # of devices that can be revoked? Absolutely ridiculous.
And yes, any data wipe would do the same thing, so I imagine if you have a phone with issues (like the Nexus) and you buy the first one, then try 2-3 data wipes/different ROMs to get signal drops/color/whatever fixed. That's 3 devices. Then, they get 2 more Nexuses, and try the same thing on the first, but the second device is fine, so they flash a ROM. That's already 7-9 devices right there. That means you can only flash 5-7 ROMs before you encounter this issue.

Amphibliam said:
Honestly, the only reasons why this isn't widespread is because people just haven't flashed enough ROMs yet. This won't just affect the Nexus, but ANY rooted Android device that flashes 15 or more ROMs in a year. Which is like 99% of the rooted population. My guess is that within 1-2 months, this will be all over the internet. I was just unlucky enough to be one of the first. But this really is absurd. What is the reasoning behind limiting the # of devices that can be revoked? Absolutely ridiculous.
Click to expand...
Click to collapse
Wiping a device has the same effect.
You don't need to flash a rom, because it doesn't change your esn, meid, or even your android_id.

I updated my post.

Amphibliam said:
I updated my post.
Click to expand...
Click to collapse
I am sure that once this issue is out in the open, it will be a rule that you can only deauthorize 4 unique devices each year. As of right now it is not differentiating between multiple instances of the same device.
I have no idea who to ***** at, but I'll support anyone who starts a complaint, petition, or whatever.

It was mentioned earlier but, what I do is restore my "accounts/sync" with titanium backup.
That way you don't have to authorize the device each time.
Be sure to:
After backing up all apps and system data, then after flashing a new ROM on first boot, install titanium backup (pro or not) VIA APK
Then run Titanium Backup and restore the accounts
Then restore the google music app with DATA via Titanium Backup
Then use the market and music like normal without any need for autorizing a new device etc..

How to force android 4.0.4 ota for verizon galaxy nexus

I saw this method in a comment on Engadget and it seemed sketchy, but I tried it and it worked perfectly.
Go to apps> all >google services framework
Force stop the app and clear data(or the other way around, doesnt matter which order)
Go to about system and then check for updates.
The phone will say it was last updated 12/31/1969....click check now and then magic.
*note: you may have to repeat these steps multiple times before it finally shows the update ...for me it was 2...but others were reporting up to 6 times

Awesome, worked like a charm for me

Works .......took about 4 times. Now to lock bootloader.
Sent from my Galaxy Nexus using xda premium

Just bear in mind that if you do this, push notifications will break in many apps like Twitter, Android Lost, GetGlue, IMDB, Instagram, etc. The only way to get them working again is to clear the data for each individual app and set it up again.
Sent from my Galaxy Nexus using Tapatalk 2

Forced OTA
All seems to work goes to green droid starts to update, he falls over with a red triangle!

oldblue910 said:
Just bear in mind that if you do this, push notifications will break in many apps like Twitter, Android Lost, GetGlue, IMDB, Instagram, etc. The only way to get them working again is to clear the data for each individual app and set it up again.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Push Notifications never broke for me
Sent from my Galaxy Nexus using XDA

schwartzman93 said:
Push Notifications never broke for me
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
They won't break in every app, only certain ones. I believe it depends on how the individual app implements push notifications.

worked for me
first time no, changed order of clear/force stop, worked

schwartzman93 said:
I saw this method in a comment on Engadget and it seemed sketchy, but I tried it and it worked perfectly.
Go to apps> all >google services framework
Force stop the app and clear data(or the other way around, doesnt matter which order)
Go to about system and then check for updates.
The phone will say it was last updated 12/31/1969....click check now and then magic.
*note: you may have to repeat these steps multiple times before it finally shows the update ...for me it was 2...but others were reporting up to 6 times
Click to expand...
Click to collapse
Thanks! Worked like a champ for me. Only had to do it twice before it updated.

worked for me!!
Took four times and worked like a charm. So happy to not have to wait any longer.

norm883 said:
All seems to work goes to green droid starts to update, he falls over with a red triangle!
Click to expand...
Click to collapse
I'm having this exact same issue, non-rooted, unlocked bootloader....anyone got any suggestions?

I had tried this numerous times on Friday with no luck, but I did it today and Boom, it's downloading now!!

Question
It took about 8 times before this worked for me. This may be a stupid question but, after the update, when rebooting my phone, I get the unlock icon as if I had unlocked the boot loader but I have never done that on this phone is that supposed to happen?

I've been trying this periodically over the last 3 days. Probably done it 30 times.
Still nothing. (Not unlocked or rooted.)

vishious89 said:
I'm having this exact same issue, non-rooted, unlocked bootloader....anyone got any suggestions?
Click to expand...
Click to collapse
Same here, except I have root. I am still completely stock 4.0.2 though, including radios.

Did the update unlock anyone else's phone?
Sent from my Galaxy Nexus using XDA

No one else has had this method appear to unlock their boot loader?

Force 4.0.4 ota update without root, unlock or anything!!!!

ONLY TRIED AND TESTED ON VERIZON CDMA VERSION.
Here is how to update you nexus to 4.0.4 ota. Just did it to my phone and worked great!!!
Go to settings
apps
google services framework
clear date
then back to settings
about phone
update
yay 4.0.4
I TAKE NO CREDIT FOR INSTRUCTIONS. FOUND ON ANANDTECH SITE

adamsautocare said:
Here is how to update you nexus to 4.0.4 ota. Just did it to my phone and worked great!!!
Go to settings
apps
google services framework
clear date
then back to settings
about phone
update
yay 4.0.4
Click to expand...
Click to collapse
u forget to mention "GSM" and "yakju"

I did that 3 hours ago and it worked found it on Android Central forum http://forums.androidcentral.com/verizon-galaxy-nexus/177456-3-clicks-im-4-0-4-a.html here are the steps i did
Home/menu/settings/apps/all/google services framework/
Touch this.
Once it opens clear data and force stop it. Hit home/settings/about phone/check for updates.
May take a few tries.

It took a couple tries for it to work for me but it did work.
Color me a happy camper. That put an end to my son's gloating that he had the update and I didn't.
Sent from my Transformer TF101 using Tapatalk 2

gadzooks64 said:
It took a couple tries for it to work for me but it did work.
Color me a happy camper. That put an end to my son's gloating that he had the update and I didn't.
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
It took a couple times for me to
Sent from my Galaxy Nexus using Tapatalk 2

Doing this will break push notifications in some apps like Twitter, IMDB, Android Lost, etc. It depends on the app. If you stop receiving notifications from an app after doing this trick, the only way to get it working again is to clear the app's data and set it up again.
Sent from my Galaxy Nexus using Tapatalk 2

I flashed 4.0.2, rebooted, and got the ota

Is there a real advantage to having the .04 OTA over a ROM that is .04?

Not necessarily, except IMM76K could have some kind of telephony code that custom AOSP ROMs wouldn't have...but we wouldn't know that for sure until IMM76K gets tagged in AOSP, if it ever does.
Sent from my Xoom using Tapatalk 2

Good to know.
I didn't want to restore to .02 and do all the hubub getting there if it really isn't necessary.
Thanks!

WOLF26915 said:
Home/menu/settings/apps/all/google services framework/ Once it opens clear data and force stop it. Hit home/settings/about phone/check for updates. May take a few tries.
Click to expand...
Click to collapse
I have tried this a million of times, still no update

What worked for me on two devices so far was yo follow instructions and clear the data/force close. Then when you go check for updates and the screen says "last checked on 12/31/1969", quickly and repeatedly press the check now button. I pressed it as fast as I could and within a few seconds it started downloading the update. On my second phone I did this on, it worked the first try.
Sent from my Galaxy Nexus using XDA

SnrSuave said:
What worked for me on two devices so far was yo follow instructions and clear the data/force close. Then when you go check for updates and the screen says "last checked on 12/31/1969", quickly and repeatedly press the check now button. I pressed it as fast as I could and within a few seconds it started downloading the update. On my second phone I did this on, it worked the first try.
Click to expand...
Click to collapse
I tried it many times but didn't work

The same for me. I have a Google Galaxy Nexus and I can't force the update from 4.0.3 to 4.0.4
I tried a lot of tricks like the one you give, and it still does not want to update... I bought it directly from Google so there is no carrier involved...

Zidd0 said:
The same for me. I have a Google Galaxy Nexus and I can't force the update from 4.0.3 to 4.0.4
I tried a lot of tricks like the one you give, and it still does not want to update... I bought it directly from Google so there is no carrier involved...
Click to expand...
Click to collapse
Well then you must have installed a non-stock ROM at some point because no Galaxy Nexus model that I'm aware of has ever had Android 4.0.3 installed on it.

This method worked for me first try, first push of the button. Thanks!
Sent from my Galaxy Nexus using xda premium

oldblue910 said:
Well then you must have installed a non-stock ROM at some point because no Galaxy Nexus model that I'm aware of has ever had Android 4.0.3 installed on it.
Click to expand...
Click to collapse
Thanks for your answer.
The fact is I was working at Google 6 months ago and so Google deployed 4.0.3 on my phone. Now that I'm gone, I'm stuck with 4.0.3 and I can't apparently update to 4.0.4. Any idea on how to change "admin" settings or downgrade to default version and then upgrade?
Thanks

I finally made the update.
I had to unlock my bootloader and then I used the Galaxy Nexus Toolkit to install 4.0.4 as the factory image. then, I used the OTA to have 4.1.1 (aka Jelly Bean).
The most important thing is to install the Android ADB Interface driver, so that your phone is available while on recovery mode.
After all these steps, you can lock the bootloader again, what I did

[Q] AT&T galaxy s3 can't check for OTA updates?

Literally every time i check for software updates i get
"Communication failed"
The server is currently unavailable.
Your device will automatically check for an update within the next 48 hours.
Then if i check again it says device is up to date, you can check for updates again in XXhours. If i go into application manager -> AT&T Software Update and clear data, i can check for updates again but i get the same communication failed. I also tried clearing data and rebooting phone, and it still wont check.
And i can't get Samsung Kies running on my windows 7 pc for some reason, so i can't get updates from there either.
Is anyone else on AT&T experiencing these problems? Any fix for this? I really want that update that adds brightness control to the notification menu.

jefferson9 said:
I really want that update that adds brightness control to the notification menu.
Click to expand...
Click to collapse
I did not update, but hearing that update would disable local search, add new modem. Nothing about Brightness control

There is no brightness control on ATT update. I was having the same problem you were and exchanged the phone. There is no fix as far as I know for the error you are getting. It is a common issue. Search the annoyances (bugs) thread.
I don't know if the OTA update resolves your issue because they day after I exchanged mine the update came out.
Sent from my SAMSUNG-SGH-I717 using xda premium

I also haven't been able to get the OTA update. I assumed it was because I rooted and the device is listed as 'modified'. Is the update worth it?

It is in my opinion, and my usage habbits, for the WiFi stability increase that is gained.
Universal search is stripped (searches conducted on phone do not include on device results, ie contacts).
In other words, if you use the Google search by long pressing your menu button the results from your search will only be pulled from the internet.
I rarely use the search built in, so it hardly mattered to me.
Check out the developer forum for ways around the universal strip if you are rooted and want to update.
Sent from my SAMSUNG-SGH-I747 using xda premium

Well i reseated the SIM card, and removed the little blue tape from the sd slot and the SIM slot, rebooted and still not working.
I wanted to avoid rooting, since the stock software runs so smoothly and i liked being on the latest at&t software. I guess since i can't get OTA updates now theres no reason not to root.
Will this issue be fixed eventually? Or would i be better off exchanging phones while i can?

I'd exchange it. If you have faulty hardware then rooting won't do anything for you.
Peace of mind, if anything, that if you decide to root your phone is functioning as it should from the start.
Others will argue it's software issues.
But, whatever the cause, none of us paid to have a 90% functioning phone from the factory. Go get what you paid for is my take on it.
Good luck.
Sent from my SAMSUNG-SGH-I747 using xda premium

the1stSecond said:
I'd exchange it. If you have faulty hardware then rooting won't do anything for you.
Peace of mind, if anything, that if you decide to root your phone is functioning as it should from the start.
Others will argue it's software issues.
But, whatever the cause, none of us paid to have a 90% functioning phone from the factory. Go get what you paid for is my take on it.
Good luck.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Well speaking as a software engineer, i'm almost certain its a software issue, most likely with at&t's software update app, or on their servers. Mabey reinstalling the at&t software update application will help?

It sounds reasonable to me. Maybe try the method for No trip flash counter in devoplment? You would be upgrading to the newest firmware and have root and not trip the flash counter. You would still be able to check for ota updates (although should just return the status of your software is up to date since it is a totally stock ROM just with root injected). I imagine that would reinstall the software update service. Although with your knowledge you are way over my head. And whether or not when updating ROMs if that application is reinstalled is something I can't answer.
Maybe just try this first:
Settings> Application Manager> All> AT&T Software Update> Clear Data> Confirm
Power off Phone
Remove battery for at least thirty seconds.
Reinstall battery and power on device.
Try again after device boots up.
Sent from my SAMSUNG-SGH-I747 using xda premium

I've been having this same problem
I was thinking that its because of AT&T's controlled release of the OTA.
Its been so long since the release, that I can't imagine that's still true. I also agree that its probably a software thing. I have a number of the bloat apps disabled and also wonder if one or more of those would interfere with such a thing.
I'd love to hear about a resolution.

k3y0n4 said:
I've been having this same problem
I was thinking that its because of AT&T's controlled release of the OTA.
Its been so long since the release, that I can't imagine that's still true. I also agree that its probably a software thing. I have a number of the bloat apps disabled and also wonder if one or more of those would interfere with such a thing.
I'd love to hear about a resolution.
Click to expand...
Click to collapse
That's an interesting theory, I've disabled some boatware too. Have you tried enabling them? I'm going to try that now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

So, if it's a software issue why is it two identical devices running the same software from the factory yield different results? I.e. my first device would do exactly as your original post outlines, then my replacement device had no issue checking for updates (same stock software, same device form factor).
If you search there are a lot of examples of complaints of this exact issue.
I am also very interested in this because even though there are many complaints out there, the only answers seem to be;
1) who cares this is xda and we update through Odin/cwm etc...
2) replace it.
Good luck, I hope you guys find an answer.
Sent from my SAMSUNG-SGH-I747 using xda premium

jefferson9 said:
That's an interesting theory, I've disabled some boatware too. Have you tried enabling them? I'm going to try that now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried enabling everything. I've tried enabling 'Samsung Push' which seemed like the likely starting point. I've been trying to do some debug on some battery drain things, so I've been hesitant to change too much at once. Also, I can basically only check every 24 hours so its slow going.
As far as the hardware issue, it just doesn't make too much sense that a hardware issue would be causing a problem because the software update would presumably be using the same hardware as the rest of the working smartphone functions. I think the explanation to one device updating and one not is more likely a server device id filtering or a user changing more than 'just the new hardware'.
Its neither here nor there though. Everyone will have there hair brained theories. Why don't we start asking what features will be on the next iphone. Seriously though, apple has to add a removable battery right? (I'm just kidding, please don't spam a million responses about how that will or will not ever happen.)

k3y0n4 said:
I haven't tried enabling everything. I've tried enabling 'Samsung Push' which seemed like the likely starting point. I've been trying to do some debug on some battery drain things, so I've been hesitant to change too much at once. Also, I can basically only check every 24 hours so its slow going.
As far as the hardware issue, it just doesn't make too much sense that a hardware issue would be causing a problem because the software update would presumably be using the same hardware as the rest of the working smartphone functions. I think the explanation to one device updating and one not is more likely a server device id filtering or a user changing more than 'just the new hardware'.
Its neither here nor there though. Everyone will have there hair brained theories. Why don't we start asking what features will be on the next iphone. Seriously though, apple has to add a removable battery right? (I'm just kidding, please don't spam a million responses about how that will or will not ever happen.)
Click to expand...
Click to collapse
You can bypass the wait time between checks by going into application managment -> at&t software update and clearing data. Then you can try to update again.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

I've had similar issues checking for updates. i gave up and pulled the first update with the USALG1 rom posted in the development forum sticky. I too have several apps disabled (actually moved out of the system/app dir) and was wondering if that possibly caused issues. I never did try updating through kies though.

My kies wont even run on my windows 7 64 bit. There seems to be alot of people having problems with kies on win7 64 bit, nothing from samsung either. So theres really no way for me to get updates

This is How I Got My Phone to Update
I should add that this was my 2nd galaxy s3 to not update. I did a factory reset hoping it would fix the issue. It didn't. I called att customer care for help b/c I was thinking maybe they just set up my account incorrectly when I first got the phone. Nothing else really makes sense. They said they couldn't help and take it to the store. I took it to an att store, and they said they don't actually do any software troubleshooting, so they just exchanged it for a new one. I tried doing the update there, it failed, so I took it home, and I force closed all the update apps, cleared all their data, and it worked as soon as I hit update. If force closing and clearing the data from the att and samsung update apps doesn't help, There may be nothing else you can do except take it in to an att shop.

AndroidLonghorn said:
I should add that this was my 2nd galaxy s3 to not update. I did a factory reset hoping it would fix the issue. It didn't. I called att customer care for help b/c I was thinking maybe they just set up my account incorrectly when I first got the phone. Nothing else really makes sense. They said they couldn't help and take it to the store. I took it to an att store, and they said they don't actually do any software troubleshooting, so they just exchanged it for a new one. I tried doing the update there, it failed, so I took it home, and I force closed all the update apps, cleared all their data, and it worked as soon as I hit update. If force closing and clearing the data from the att and samsung update apps doesn't help, There may be nothing else you can do except take it in to an att shop.
Click to expand...
Click to collapse
When you got it to work, exactly what apps did you force close and clear data? Just AT&T software update? Any others?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I force closed the At&T Software Update app and I think the Samsung Push Service. It is really the AT&T software update app that finally started downloading immediately after trying it again.

So I finally attempted the Keis connection and it worked immediately. I don't know what other problems people are having, but when I installed it on my Win7 x64 machine I had the S3 connected. After I ran the software for the first time it mentioned an update and proceeded to update it. Keep fighting the good fight jefferson9.

Can't update my phone in any way

Hey guys, I'm new here, so this thread is probably on here somewhere, but oh well. I can't update my S3 OTA or through Kies. I know there is an update, as my friend got it fine on his yesterday (it's the one with the brightness slider in notification center). On OTA, it says communication failed every single time, then says up to date. I have tried clearing data and all that as well. And in Kies, it also says I have the latest firmware, even though I know I don't. Any ideas? I really don't want this happening when Jelly Bean comes out. Oh yeah, I'm not rooted or anything by the way, I'm still on stock for now.

I have the same exact issue. I think it has something to do with ATT and the phone not being set up right in their system. Did you by chance have an iPhone before your S3 and use the same Sim card?

Mine wouldn't find the ota on the phone. I searched around here and found a thread someone had started that has instructions on how to download the flashable zip and install it via CWM. Worked like a champ. If you are rooted this is the way you'll want to go
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Yes I did come from an iPhone. And I am planning to root soon so I might have to try that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Hey do you mind giving me instructions on how to do that? And is there a safe way to root my phone on a Mac? And last of all, can I still get updates such as Jelly Bean on a rooted GS3 without losing root without messing anything up? Sorry I'm coming from iPhones and jailbreaking so I'm not familiar with all this.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Vanillamarble said:
Hey do you mind giving me instructions on how to do that? And is there a safe way to root my phone on a Mac? And last of all, can I still get updates such as Jelly Bean on a rooted GS3 without losing root without messing anything up? Sorry I'm coming from iPhones and jailbreaking so I'm not familiar with all this.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I've always recommended returning whatever device you have back to 100% stock (as it was out of the box) before taking any official updates. I've heard ppl say they can take them just fine while still rooted - but they lose root. Sometimes you can simply re-root, sometimes you have to wait for a new exploit to be discovered before you can root again. In light of this, I always wait a week (sometimes less) after a new OTA (Over The Air) update is released, just to be sure I can regain root immediately. Welcome to the wonderful world of Android OS!!!
[edit] to answer your post about not being able to take the last OTA update. Have you tried a factory reset? Through Android Recovery? You will lose personal settings and contacts if you dont back them up. But, it may solve your update issue. Another thing I know, that a lot of ppl do is - as soon as you buy a new device, such as the awesome Galaxy S III, is to immediately do the factory reset. (Who knows how many employees have goofed around with the new toys they just got in stock)

I had the same problem with not being able to get the OTA update on my S3. Turns out it was a bad sim. As soon as I got a new sim from AT&T everything worked fine. Wish I would have done that first cause I spent hours on the phone with AT&T and Samsung trying to fix the problem. Good luck. Hope that works for you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Same issue here. Just spent a couple hours this Saturday at an AT&T store - end result is that they are swapping it out under the manufacture 1 year warranty.
Sim replacement did not fix it for me.
Tech support over the the stores land line says that the option to push OTA to phone is greyed out and not selectable with my account.
They are sending me a new phone so we'll see.

G-Man. said:
I've always recommended returning whatever device you have back to 100% stock (as it was out of the box) before taking any official updates. I've heard ppl say they can take them just fine while still rooted - but they lose root. Sometimes you can simply re-root, sometimes you have to wait for a new exploit to be discovered before you can root again. In light of this, I always wait a week (sometimes less) after a new OTA (Over The Air) update is released, just to be sure I can regain root immediately. Welcome to the wonderful world of Android OS!!!
[edit] to answer your post about not being able to take the last OTA update. Have you tried a factory reset? Through Android Recovery? You will lose personal settings and contacts if you dont back them up. But, it may solve your update issue. Another thing I know, that a lot of ppl do is - as soon as you buy a new device, such as the awesome Galaxy S III, is to immediately do the factory reset. (Who knows how many employees have goofed around with the new toys they just got in stock)
Click to expand...
Click to collapse
Read through the thread guys - there are other answers given besides just swapping the sim card...

Ok I'm going to try a factory reset. Wish me luck guys.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Just did a factory reset, and it didn't help at all. Now I've got to get everything back on my phone. Coming from iPhone, I will say that Apple has a heck of a lot better backup system. I do 0refer my GS3 though. Ok so any suggestions now?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

you've tried to update over cell network AND WiFi... correct? same error each time?
I'm not sure what else to suggest except trying a new sim card like someone else suggested... beyond that, a replacement device. Sorry man, wish I could be more useful...
[edit] The only other thing I can think to try would be to completely remove all your current USB Drivers for Samsung from your PC and reboot the PC, then re-install the USB Drivers, and try Kies again. If it still doesn't work, try a different PC.

Well I'm going to try a different computer, and if that doesn't work, I'm going to an AT&T store. Thanks for all the help guys.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app