Develop Bugs

Switching Carrier and Phone need help getting data

I am switching both carriers and phones. I am moving from ATT with the SG2 to T-Mobile to the SG2.
I have invested tons of time setting up my ATT version and loads of data in my apps. I am not worried about the Mail/Exchange part I realize I will need to redo that part. What I am hoping someone can help me with a way to move over is the following: (Also I am NOT ROOTED)
1. Touchwiz screens
2. Application data from Market downloaded apps
I realize I can reinstall the apps but the data from the apps is my issue. I track expenses etc using several apps.
TIA,
ED

Without root you're sol mate
Sent from my Hercules with xda Premium.

a couple of things re: data
as far as emails goes, if you are hooked up to Exchange Server or Gmail
your email resides on the server side, and stays there.
but if you are using POP3 emails that have been downloaded to the phone and removed from the server, then you will be stuck, unless you get Titanium Backup (which needs root) to migrate the emails over to the new phone

kenvan19 said:
Without root you're sol mate
Sent from my Hercules with xda Premium.
Click to expand...
Click to collapse
Well thats not the answer I was hoping for. I would prefer to not root install Titanium and reflash since I am returning the SG2 back to ATT. I don't want something to go wrong.
I'm still hoping for a better answer.

kenvan19 said:
Without root you're sol mate
Sent from my Hercules with xda Premium.
Click to expand...
Click to collapse
What this guy said.

[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.

Amazon app store and JB 4.2

Since upgrading to JB 4.2 the Amazon app store keeps having me authenticate periodically. I assume that this is related to the JB update, but I haven't seen anyone else mention this issue. Particularly when accessing Tweetcaster Pro is when I see the issue start, but then no other app works correctly.
Just for some background, I wiped my phone yesterday with 4.1 and then installed 4.2. I have the latest version of the app store and have tried clearing cache/data, uninstalling, reinstalling. No help.
So I'd like to know if anyone else is seeing this or if it is just me.
Thanks

Probably just needs a compatibility update, same as every other app that isn't working on 4.2 right now.

WiredPirate said:
Probably just needs a compatibility update, same as every other app that isn't working on 4.2 right now.
Click to expand...
Click to collapse
Thanks. I figured that was the case. I would just be more at ease knowing I wasn't alone.

Same behaviour here after updating to 4.2. Hope Amazon is fast with a fix...

Same here - driving me freaking crazy

You may have to redownload the Appstore apk, there seems to be one with a new layout now.
Sent from my Galaxy Nexus using Tapatalk 2

It kept asking me to sign in and when I did it was saying wrong password even though I knew it was right. I only had about 3 paid apps for free that I still used so I just uninstalled them and purchased from the play store and uninstalled the amazon app store.....haven't "bought" a free app in like 3 months...the selection is getting to be crap
Sent from my Nexus 7 using Tapatalk 2

turdbogls said:
haven't "bought" a free app in like 3 months...the selection is getting to be crap
Click to expand...
Click to collapse
Ain't that the truth.

Johnassel said:
Same behaviour here after updating to 4.2. Hope Amazon is fast with a fix...
Click to expand...
Click to collapse
Sorry for you, but glad to hear it. I ended up calling them today and they hadn't heard of any issues. I suspect they know now.

I'm getting the same thing too although my login credentials actually work. The one thing I haven't checked is whether or not these logins are creating a new device authorization every time.
I completely wiped my phone before upgrading to 4.2 and Amazon App store and Verizon FiOS Mobile Remote are the only two apps with issues.

I have the same issue with Forum Runner. Every time I close the app I get signed out and need to re-login every time I open it back up. So annoying but I'm guessing its a 4.2 update thing. I've deleted it and re-downloaded it and it made no difference.
Sent from my cell phone

turdbogls said:
..haven't "bought" a free app in like 3 months...the selection is getting to be crap
Click to expand...
Click to collapse
I know that feel, I just uninstalled it altogether.

WiredPirate said:
I know that feel, I just uninstalled it altogether.
Click to expand...
Click to collapse
Unfortunately, I have a few FAOTD that I use frequently, so I have to keep it installed.

pwc realtor said:
The one thing I haven't checked is whether or not these logins are creating a new device authorization every time.
Click to expand...
Click to collapse
They explained to me that everytime you login, it creates a new device instance. They limit it at 25. I hit that mark yesterday.

coreyva said:
Unfortunately, I have a few FAOTD that I use frequently, so I have to keep it installed.
Click to expand...
Click to collapse
I've read that in the past, but it's never been true for me. I use TubeMate from Amazon and dont need the Amazon Market installed to do so.

Having the same issue with the app store. Just got off the phone with amazon and they are aware of the problem and are working on a fix now

coreyva said:
They explained to me that everytime you login, it creates a new device instance. They limit it at 25. I hit that mark yesterday.
Click to expand...
Click to collapse
Ouch! I just logged in to my Amazon account and saw all the "Nexus 7 xx" devices that were registered.
Thanks for the heads up. I deregistered all the new devices.

This worked for me
From another forum I found this solution to work:
1) Delete Google Account
2) Reboot Device
3) Reactivate Google Account
4) Log on with Amazon Appstore App
All apps load and run without need to log on each time now.
I also deleted excess Amazon devices as noted above.

Bishop Scientifics said:
From another forum I found this solution to work:
1) Delete Google Account
2) Reboot Device
3) Reactivate Google Account
4) Log on with Amazon Appstore App
All apps load and run without need to log on each time now.
I also deleted excess Amazon devices as noted above.
Click to expand...
Click to collapse
seems like it does not work for me.
still working for you?

Yeah it does add a new device each time... I have 7! Deleted 6 of them... still same problem.

Error 927, And All Potential Solutions Have Failed...

Here it is in a nutshell: Error 927 on ANY download, any app, any game, be it paid or free, on my Nexus 7 (2013) FHD. I've done the following:
- Cleared the data and cache for the Google Play Store, Download Manager, and Google Services Framework.
- Uninstalled updates for the Google Play Store and Google Services Framework.
- Deleted and re-added my Google account.
- Rebooted.
- Hard reset.
- Downgraded to 4.3 and re-upgraded to 4.4.2.
- Tried to download the apps and games from the Google Play website, and get "An unexpected error has occured. Please try again later."
- Changed the filter and proxy settings on my Cisco router.
- Switched to LTE, and... same thing.
- Created another Google account, and it worked, but I will NOT be forced to re-purchase the apps I've spent nearly $80.00 on over the years, or upload my music collection to Google Music again.
- Reached out to Google for help, and... crickets.
I'm at the end of my rope. If this isn't resolved soon, I'm returning the Nexus to Wal-Mart. I've NEVER had this sort of issue before, even with my first-generation Nexus 7. I've had Android tablets since my Motorola Xoom awhile back. I've ALWAYS had Android tablets. I'd hate to have to abandon Android because of this idiocy, but I may have to do so. I don't want to have to go with Apple for both my smartphone and tablet, but it's starting to look that way.
If anyone has any suggestions that aren't listed above, please, help me out. I love my Nexus 7, but without apps and games, it's pretty worthless.
Thanks in advance.

Normally deleting and adding back the Google account is a solution for Play Store problems, but as you said, you tried that. Some have reported that error 927 is because of a network connection error. How is web browsing? YouTube?
abarax said:
- Downgraded to 4.3 and re-upgraded to 4.4.2.
Click to expand...
Click to collapse
How did you do that? Did you download the 4.3 ROM to flash it? Did you unlock and flash a custom recovery?
When all else fails, flash the stock ROM, especially with your downgrading and upgrading. Google's files include a "flash-all.bat" within that will wipe everything and flash the stock ROM and recovery.
https://developers.google.com/android/nexus/images#razor

Pandae said:
Normally deleting and adding back the Google account is a solution for Play Store problems, but as you said, you tried that. Some have reported that error 927 is because of a network connection error. How is web browsing? YouTube?
All web browsing and pre-installed apps work just fine. Just any attempts to update those apps, or install any other apps from Google Play, fail with error 927.
How did you do that? Did you download the 4.3 ROM to flash it? Did you unlock and flash a custom recovery?
When all else fails, flash the stock ROM, especially with your downgrading and upgrading. Google's files include a "flash-all.bat" within that will wipe everything and flash the stock ROM and recovery.
https://developers.google.com/android/nexus/images#razor
Click to expand...
Click to collapse
I actually have flashed the stock ROMs, from the original 4.3 to 4.4.2, with the exact same results. I've also made certain not to unlock the bootloader and to not root as to recreate the OOB experience as well. At this point, my options are exhausted.

abarax said:
I actually have flashed the stock ROMs, from the original 4.3 to 4.4.2, with the exact same results. I've also made certain not to unlock the bootloader and to not root as to recreate the OOB experience as well. At this point, my options are exhausted.
Click to expand...
Click to collapse
Are you able to install apps on another device with the same account? If not it may be a problem with your account...

Dexxon said:
Are you able to install apps on another device with the same account? If not it may be a problem with your account...
Click to expand...
Click to collapse
I know his pain I have flashed reflashed installed stock and im using a atrix 2 with ics 4.0.4
im hoping its a google server problem and it will be fixed

I was having the same problem for the last two days and I went to settings/Google account and noticed there was a sync error with sound search for Google play and I manually synced it and now apps download .
Sent from my Nexus 5 using Tapatalk

I went into my account removed my devices from it on the web and signed in on my phone now it works
Sent from my MB865 using Tapatalk

I've been having the exact same issue for 4 days. Regardless of rom, phone, or gmail account I use. I've done every wipe format imaginable even Odin as I have a Samsung phone same issue. Now I cant even get any Google apps to connect at all. Such as Google plus play store YouTube etc...Google says never heard of it before sorry.

dawiseguy77 said:
I've been having the exact same issue for 4 days. Regardless of rom, phone, or gmail account I use. I've done every wipe format imaginable even Odin as I have a Samsung phone same issue. Now I cant even get any Google apps to connect at all. Such as Google plus play store YouTube etc...Google says never heard of it before sorry.
Click to expand...
Click to collapse
I'm having the exact same problem now for a few days. I called Google support and they are aware of the problem and had no resolution. I was told too bad basically.
Out of curiosity, for those having this issue, did you upgrade to a 4.4.2 ROM?

I updated to stock rooted 4.3 galaxy note 2 Verizon and it happens on all of my gmail accounts too
Sent from my SCH-I605 using Tapatalk

I have the same problem. Ran across this thread doing a search for the error 927. Running a Verizon HTC One and an LG G Pad 8.3. Both have the same problems, and i too have called Google several times. Their answer was to call HTC. I was livid. I changed my password, but was only a temporary fix until I made a purchase from the Play store. Then the error came back. I realize i am in the Nexus 7 forums but wanted to chime in since the problem is happening to me too. Hopefully Google comes up with a fix. Too much money tied up to just create new account, which does work by the way.

Creating a new account shouldn't even be an option what it the issue happens on the new account? Google just needs to fix it.
Sent from my SCH-I605 using Tapatalk

dawiseguy77 said:
Creating a new account shouldn't even be an option what it the issue happens on the new account? Google just needs to fix it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I agree...I would be ok if they just said we're working on a fix, but just to ignore me and say call the manufacturer pizzed me off.
Sent from my HTC6500LVW using Tapatalk

planedoc said:
I agree...I would be ok if they just said we're working on a fix, but just to ignore me and say call the manufacturer pizzed me off.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Yeah Google making me mad too
Sent from my SCH-I605 using Tapatalk

Same boat. I did everything the original poster did as well. Called into play store support and eventually got passed off to tier 2 support. Haven't heard anything in over a week.
The issue affects every device I log into with my account. Originally showed rpc:s-7 error, now 927.
Anyone with this problem find a solution? Again, I've done everything the op posted. In the past I've been able to correct the problem. But this time, no go.

Have the same problem... In every device I'm using with my account... 3 tablets, 2 cell phones. Spent more than 400 dollars in apps.. Can't download, nor even update. Always error 927. Changed password and problem persists.. It's obviously a problem with my account.. Wonder what could I do.

Have you tried installing apps from Google Play on a computer?

Hello, just an update...
My problem has gone... Seems it was from google side.
Too bad I had to flash my cel 3 times before I realized it was happening to all my devices.
Don't know if the password change had anything to do with the fix since, at least, it didn't work immediately.
If you encounter the same problem don't panic... give it a little time, hopefully it fixes on its own.
Thank you very much.

When does the official Lollipop update push over the air?

I'm reluctant to root and install a custom ROM. When does the official Lollipop update push over the air for our Nexus 7 (2013) WiFi?

It's being pushed right now, but gradually.
Sent from my Nexus 7 using XDA Free mobile app

im still waiting.. damn slow
Nam Huy Linux http://www.namhuy.net

What does gradually mean? :silly: Just kidding.
The availability was supposed to be November 12th. By now, all Nexus 7 owners were supposed to receive the update.
Jhall8 said:
It's being pushed right now, but gradually.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse

arjun90 said:
What does gradually mean? :silly: Just kidding.
The availability was supposed to be November 12th. By now, all Nexus 7 owners were supposed to receive the update.
Click to expand...
Click to collapse
Good one! Gradually=ssssllloooowww aaaasss heeeeellllll afaik
Sent from my XT1080 using XDA Free mobile app

Darn it. That's Google's way of wishing us Merry Christmas. :good:
Jhall8 said:
Good one! Gradually=ssssllloooowww aaaasss heeeeellllll afaik
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse

No OTA for me yet....

No OTA for me too

I'm waiting, too.
Sent from my Nexus 7 using XDA Free mobile app

Waiting here as well for my nexus 7 2013...... (but my brother received two days ago on his nexus 7 2012).

I have two Nexus 7 2013's each on different Google accounts and to date '0 for 2' on this update. Phantomware to me so far. Tick-tock...

Same here... No Lollipop yet.

Still no update here yet in UK... Yet my missus got her update on her nexus 7 2012 few days ago

Yep. My old 2012 Nexus 7 got it a couple of days ago, my Nexus 5 got it a few hours after that, but still waiting on my new Nexus 7.

You can backup your existing data on your Nexus 7, then flash the Stock Factory Image that Google provided and install and enjoy... The first boot though takes 5-7 mins.. Restore your personal Data, NOT the data partition.. Lollipop handles the file structure a tad differently..
https://developers.google.com/android/nexus/images
Edit: when installing a factory image, it completely wipes your device, verses an OTA..
If you look hard enough you can find someone who has posted the OTA here on XDA..
But if you are rooted, using Xposed, Custom Kernel, or a Custom recovery you will not be able to update..

Zaphodspeaks said:
You can backup your existing data on your Nexus 7, then flash the Stock Factory Image that Google provided and install and enjoy... The first boot though takes 5-7 mins.. Restore your personal Data, NOT the data partition.. Lollipop handles the file structure a tad differently..
https://developers.google.com/android/nexus/images
Edit: when installing a factory image, it completely wipes your device, verses an OTA..
If you look hard enough you can find someone who has posted the OTA here on XDA..
But if you are rooted, using Xposed, Custom Kernel, or a Custom recovery you will not be able to update..
Click to expand...
Click to collapse
This misses the point of having a Nexus. This is XDA I am sure people know they can flash it. The point of a Nexus is to get the updates right away from google. I have other devices which I flash roms on but bought a Nexus for the pure google experience.

krispy1 said:
This misses the point of having a Nexus. This is XDA I am sure people know they can flash it. The point of a Nexus is to get the updates right away from google. I have other devices which I flash roms on but bought a Nexus for the pure google experience.
Click to expand...
Click to collapse
There is trick, I forgot how or what.. But it resets the Google cache, and you hammer on update and sometimes rather than not.. the update would pop up.. Someone please remind me of how that is done, I just find the OTA here and sideload it, or install the Factory image..
They are rolling the updates in certain areas in a controlled manor so if something really bad pops up that can stop it from hitting every device at once

If you've never seen this , give it a read, explains why the OTA may have not reached your device yet.
http://www.reddit.com/r/Android/comments/1r1dz4/44_kitkat_has_started_rolling_out_on_the_n4/cdiwt6f
Rollouts are conducted in phases. Typically they start at 1% of devices for around 24 - 48 hours; we watch the return rates and resulting device checkins and error reports (if any), and make sure nothing looks wrong before sending it to more. Then typically it goes to 25%, 50%, 100% over the course of a week or two.
What the percentages mean is that when your device checks in, it has a 1% chance (for example) of being offered the OTA. If it doesn't (randomly) get an offer, it will never get an offer until the next batch.
IOW, once your device checks in and gets turned down, that's it until the next batch. Mashing on the "check for updates" button just causes your device to check in again, and get automatically turned down again.
Click to expand...
Click to collapse

Neomagus, That's good info. I'm wondering at 8 days out whether we have days to wait vs another week or two to wait.
Sent from my XT1080 using XDA Free mobile app

Zaphodspeaks said:
There is trick, I forgot how or what.. But it resets the Google cache, and you hammer on update and sometimes rather than not.. the update would pop up.. Someone please remind me of how that is done, I just find the OTA here and sideload it, or install the Factory image..
They are rolling the updates in certain areas in a controlled manor so if something really bad pops up that can stop it from hitting every device at once
Click to expand...
Click to collapse
A google engineer replied to this on reddit
"Doing this changes the primary ID by which Google knows your device. As far as the servers are concerned, the device was basically factory reset. There are many downstream effects of this, but a big one is that this invalidates the tokens used by any app that uses GCM (which is nearly all the Google apps, and a ton of third-party apps.)
How apps react to GCM IDs changing varies by app. With Play Store you have to log out and log back in, I think Gmail usually handles it transparently eventually but won't get new mail notifications for a while, etc. Some apps you may have to clear data on to recover. All apps will simply stop getting GCM push-messages, until they get a new GCM ID; some do this frequently, others rarely, and some apps use the GCM ID as an ID on their own servers (as it is opaque and basically random), so other things besides push messages may not work.
Nothing bursts into flames, but it makes a ton of nuisances on the device, including some that can look pretty mysterious. Your mileage will vary depending on what apps you use.
All of this can be avoided by just doing an 'adb sideload' if you are impatient."
http://www.reddit.com/r/Android/comments/1r1dz4/44_kitkat_has_started_rolling_out_on_the_n4/cdiwt6f