Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
If you haven't received the OTA update yet try this:
- Try Settings - Manage APPs -> ALL->Google services Framework: clear data
- Go to dialer and put in *#*#2432546#*#*
If you did the code right the numbers will disappear and you will get a notification that says “check in complete” or something to that effect.
Wait a second or two and if there is an update you will see something in the notification bar.
EDIT: Try doing this with wireless *off*
Good luck!
Nexus S i9020A
Rogers in Ont.
would be interested to see how this works out for you. am in canada as well but with telus in mtl although phone is just an unlocked version.
wondering though what thie google services framework app actually is, and what i'm wiping when clearing data for that app.
saw also that there's a zip for manual install. unsure how to do manual install, and wondering about risks of bricking phone or losing data in doing manual update.
It has worked out well with me! No face recognition but that's okay. I'm busy uninstalling all the programs that I used that are now included in the new version. Battery seems okay but it's only been 12 hrs (mostly overnight so no usage) and it's 70%.
Wifi is still so so (thought it would improve but I guess that's a pipedream).
Overall it seems much 'snappier'. Looking forward to playing for a few days to see what my overall impression is.
I wasn't ready to try a zip version. I've read that others on Telus have the update. Have you tried the 'checkin' ?
I have 2.3.4 AT&T version and it errors out trying to update....
Thanks for posting these official versions.
Hey guys, I am having a problem with the new update and wondered if you could help out.
So I have the 2.3.6 version of AT&T Nexus S, and I am able to download the update and rename it update.zip and get into the recover mode and apply update from /sdcard...
At that point it displays the following:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: file_getprop("/system/build.prop"
. "ro..build.fingerprint") == "google/sojua/cresp
o:2.3.6/GRK39F/189904:user/release-keys" ||
file_getprop("/system/build.prop". ro.build.fingerprint") == "google/sojua/crespo:4.0.4/IMM76
D/299849:user/release-keys"
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
It has done this twice now I have downloaded the package once on a Fedora system at work mv to a new file name and applied, and once here at home on a windows system (thinking download may have been corrupt)
I would most appreciate any thoughts on this message.
Thanks in advance.
Saw on the XDA forums that users encountered this when something was funky with their SD card, suggested a backup and reformat of it, and then putting the update.zip on there for the bootloader. Giving this a try now and will update.
I had a problem with an update on an HTC Desire where it wouldn't update although it should have. I did a factory reset and ran the OTA update again and it worked fine. I think some of the apps we install are not 100% compatible and cause issues. As a matter of course, I now do factory resets BEFORE and AFTER an update to ensure there is no junk left behind and the firmware has a clean slate to work with. Since then, no issues any time I do a firmware update.No go on this as well. I don't know what I am doing wrong here. My next thought is to try a factory reset and give it a blank slate to update. I don't know if that will work either.

I had a problem with an update on an HTC Desire where it wouldn't update although it should have. I did a factory reset and ran the OTA update again and it worked fine. I think some of the apps we install are not 100% compatible and cause issues. As a matter of course, I now do factory resets BEFORE and AFTER an update to ensure there is no junk left behind and the firmware has a clean slate to work with. Since then, no issues any time I do a firmware update.
YMMV.
Let us know the outcome of your situation...

So after a factory reset I still get the same exact error, I just don't know what is causing it.
Google phones, like the Nexus One, Nexus S, and Galaxy Nexus do not have any carrier related software. You can buy the phone at any store and it will be the same as any other location. In fact, the only difference between the boxes is the carrier code on the outside so the IMEI is already registered with the carrier. Other than that, all Google phones are the same. All the info needed to get your GSM phone up and running is on the SIM card.Would it make a difference that my phone was purchased at best buy and not at an AT&T store and doesn't have the AT&T bloatware on it? Or do none of the Nexus S hand helds have that?
Google phones, like the Nexus One, Nexus S, and Galaxy Nexus do not have any carrier related software. You can buy the phone at any store and it will be the same as any other location. In fact, the only difference between the boxes is the carrier code on the outside so the IMEI is already registered with the carrier. Other than that, all Google phones are the same. All the info needed to get your GSM phone up and running is on the SIM card.
Now about your update issue. Is your phone rooted or running a non-stock ROM? If so, you may need to flash the stock ROM.
If you have a stock ROM, then you did a factory reset, but did you try wiping the cache as well? To do this, you need to go into the Recovery Mode and select "wipe cache". While there, also do another reset, then reboot the phone.
Are you sure you're on v2.3.6 and not v2.3.4?Completely stock phone no funny business. I did clear the cache once tried the update still no go, then did the factory reset and tried with no go. Really curious still haven't heard of others struggling so.
Are you sure you're on v2.3.6 and not v2.3.4?
Yep, that's what the about phone tab says for android version.
Quite likely yes...that's an earlier build of v2.3.6 that had the tethering problems so it may not be compliant. You will need to manually update the device to v2.3.6 build GRK39F using Recovery Mode and go from there.I notice in the error it shows GRK39F but build number on my phone is GRK39C. Could this be the root of my problems?
Hey, just to tell you I (again) got back to 4.0.3 - ROM and Kernel didn't improve the battery at all, and a lot of apps lagged.start a new post so i can walk you through.
Quite likely yes...that's an earlier build of v2.3.6 that had the tethering problems so it may not be compliant. You will need to manually update the device to v2.3.6 build GRK39F using Recovery Mode and go from there.
...
News (4/2/2012): Great news for AT&T Nexus S users! A 4.0.4 update is now available for the I9020A. The update is intended for those on 2.3.6. It is unclear whether or not it will work for older versions.
I9020A 2.3.6 to 4.0.4 Link: http://android.clients.google.com/packages/ota/google_crespoa/IEzMw3FU.zip
...
Links to official update files:
...
I9020A (2.3.6 to 4.0.4, might work with Pre-2.3.6 versions) - http://android.clients.google.com/packages/ota/google_crespoa/IEzMw3FU.zip
...