yashsingh1/xdaforums huggingface dataset:
[Nexus S General] draugaz:
To me it sounds like a very strange conspiracy theory. If google would intend to do such a thing, they could simply remove the corresponding recovery menu item and be done with it.

Normal users would be stuck, and more advanced would still use CWM and avoid that restriction.

It just does not make any practical sense. If I wanted to restrict it just to the OTA users it would be so much simpler to do it using some cryptography.
[Nexus S General] mtothearkus:
I was able to update with stock recovery,was on 2.3.6 and did the incremental update to 4.0.3 and 4.0.4 in one step with stock recovery (2.3.6)
[Nexus S General] rasengan82:
That works cuz you were still on the GB recovery.
[Nexus S General] qorron:
I haven't found any evidence in the updater-script, that it checks something and umounts the /cache if something isn't right just to cause an error.

The only 'mount' line in there is the first one which mounts /system

Also, the problem only exists for incremental updates for there are no checks what so ever in the full update. Thats why it is possible to flash a full 2.3.6 or 4.0.3 over the 4.0.3.

If I where asked to make any guesses, I would suspect a bug in the stock recovery of 4.0.3 or of all ICS roms that just prevents the /cache to be mounted.

I've studied the source a little bit to understand whats going on.

If there is a bug, I haven't found it yet.

I've searched the commit messages for a hint that this behavior is intentional.

I've found nothing so far.

Maybe someone wants to downgrade to a 2.3.3 version just to get an OTA link for a full 4.0.4, which should work just fine on the ICS recoveries. ;-)

(I assume that it exists, but just no one who cares has has a version old enough to get a full OTA)

I'm very sure, that this is a bug in in the recovery. Because if it would be intentional, it's implemented in a very bad way, and it is even flawed.

They could have just removed the option if they don't want that.

Just thinking of Occam's razor.
[Nexus S General] Budge_uK:
Worked a treat for me from 4.0.3 on my i9023 without any kind of wipe. Thanks!
[Nexus S General] Jygar:
Manage to do it by unlocking the boot loader and installing CWM.

Then flashed 4.0.3 full, followed immediately by 4.0.4.

Then relock the boot loader.

That way it restore the default recovery.
[Nexus S General] mindwalkr:
I seem to be having a problem... it keeps popping up (like every 10 mins) a small triangle notification on the notification bar claiming that I changed my account or my password is wrong. However it is right.. I am authenticated in Google Play and so on.. however the Google webpage in the stock Browser has a link to sign in..

If I authenticate on the triangle as requested, it goes away and comes back in 10 mins... the browser keeps showing all the time "Sign In" on google's home page...

bananas!

maybe I'll delete my account and create it again... anyone else experiencing the same ?
[Nexus S General] jurvyx:
Same steps for i9023? Or I need to do something different?:o
[Nexus S General] thegtfusion:
Do you have CWM installed?

if yes, then do a full wipe and flash this.

exactly the same without the difficult steps.

just the same 4.0.4 stock rom, also rooted

http://xdaforums.com/showthread.php?t=1569509
[Nexus S General] david279:
Factory images now available for the nexus s.

https://groups.google.com/forum/m/?fromgroups#!topic/android-building/b50nY_onbP4
[Nexus S General] bozzykid:
Awesome. Still a shame they left out the AT&T version although apparently he can't release the images until there is an OTA for it.
[Nexus S General] haturaya:
Great! Anyone care to give it a try?
[Nexus S General] bozzykid:
All you have to do is flash it using fastboot. It is quite simple.
[Nexus S General] Skillz1318:
Same here on 9020a from custom 4.0.3 rom and kernel.
[Nexus S General] demo23019:
USB transfer still slow app drawer still micro stutter but I use apex

just as fast and smooth as 4.0.3 I see no difference

Any idea on changes?
[Nexus S General] dbol_l:
OTA in Illinois is live just did the update everything went smoothly no errors.
[Nexus S General] Flash05:
sir can you post the url to download the "recovery-clockwork-touch-5.8.0.2-crespo.img". i check the clockworkmod website. only rom manager and tether...

thanks.
[Nexus S General] GRS10:
Fastboot can load TGZ files? The link above is a .tgz...
[Nexus S General] david279:
Extract the img files out of it.
[Nexus S General] damengual:
NS i09092t

was running 4.0.3 that I had updated cleanly from CM7

backed up with CWM touch...so i originally tried updating to the 4.0.4 leaked OTA release. this caused a dead phone, restored my 4.0.3,

downloaded IMM76D_deodexed. wiped data, etc. flashed IMM76....flashed superuser just in case. booted into clean 4.0.4!

rebooted into CWMT and did a nandroid advanced restore of my data. after reboot phone updated all my apps from 4.0.3-4.0.4 was running a little choppy. rebooted.

phone is running amazing now, been enjoying ICS for all it's bugs since 4.0.3 leak, speed of interface and battery performance are amazing.

Ice cream win
[Nexus S General] sluma:
oops I forgot to quote Flash05's post.

Sure thing :)

http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-crespo.img

it's on the same page as the ROMS
[Nexus S General] Flash05:
thank you! ;)

i didn't see that part :(

so I need to replace the 4.0.3 recovery via ADB and then i should be able to update it via after using CWM...

---------- Post added at 11:36 AM ---------- Previous post was at 11:35 AM ----------

can i use the non-touch? weird right. you already mentioned use touch..

just curious :)
[Nexus S General] Lazer Bear:
Well, technically you are replacing the recovery via fastboot, not adb, but you got the hang. You can also use non touch recovery, touch is more user friendly though.
[Nexus S General] gwong76:
hi all, it seems that I am having trouble getting back into recovery after I flashed the update 4.0.4 using CWM recovery..I am on a rooted stock 4.0.3 before the update.....

When I reboot the my I9023 into fastboot mode and go into recovery it shows me a green little android with a red exclamation mark...

I tried to flash the CMW recovery image using CMD prompt...but it failed to push the recovery image file in to the phone. Can anyone help on this? Thanks.
[Nexus S General] iboj007:
Here's my experience getting to 4.0.4 on a white i9020a. A little bit more of a headache than I would have liked but nonetheless, I have it running smoothly AND I kept ALL of my data, messages, settings, etc.

I got my 9020a back in July and I believe had messed with some settings that caused it to go into a constant reboot. Basically I ended up flashing the wrong GRI54 (the one for the 9020T) and that eventually got updated to GRJ22 2.3.4.

From July until December I was stuck on 2.3.4 as I kept on trying to apply the 2.3.6 update for the 9020a and kept getting error status 7 using both stock and CWM. I had given up. Then in late December I received a brief notification to update to 4.0.3 and that update failed (also status 7).

Last week I got tired of 2.3.4 and thought about trying the full update for the 9020T thinking that maybe I had a 9020T ROM. It worked without a hitch and literally 10 minutes later I was up and running on 4.0.3 from here (http://xdaforums.com/showthread.php?t=1398186). I flashed the XXKB3 radio from the radio thread via fastboot and was sitting pretty. The battery life was horrible and KB3 had issues maintaining a signal.

Today, I downloaded the 4.0.4 file from here: (http://xdaforums.com/showthread.php?t=1569116) and tried to apply it via both stock recovery and CWM and both failed with the dreaded status 7 error. Here's what I did to get it working on the 9020a from 4.0.3

1. Backup EFS folder to a secure location.

2. Download and place the full ROM for 4.0.3 from the above thread on your SD card.

3. Download and place the update for 4.0.4 from the above thread on your SD card.

4. Download the radio UCKE1 from the thread here and place on SD card: (http://xdaforums.com/showthread.php?t=1116884)

5. Install CWM (I used CWM touch)

6. Boot into CWM and install from SD card. Install the full version of 4.0.3 (works even if you are currently on 4.0.3. This will make you stock again.)

7. Before allowing your new 4.0.3 to boot, go back into CWM.

8. Go to install zip from SD card again and install the 4.0.4 build. It should show you that it's patching the existing setup.

9. Once 4.0.4 has installed, restart the phone and allow it to boot.

10. Make sure CWM is installed and boot back into CWM.

11. Apply zip from SD card and apply the zip for UCKE1. UCKE1 was the only radio that gave me signal on AT&T. If you dont have signal, delete the contents of your /EFS folder and then replace them from your EFS backup.

12. Use your favorite rooting method to regain root. I used the 1 click method from here: (http://xdaforums.com/showthread.php?t=1544940)

ENJOY!
[Nexus S General] mindwalkr:
Is there any advantage in installing these if you have apparently already successfully updated via the incremental OTA ?

I mean.. of course there can be always something that's "slightly" of as opposed to installing a fastboot image.. but then restoring all the data again can be a pain, even if you use Titanium Backup I'm not so sure it's smooth as butter.
[Nexus S General] qorron:
Sort of comclusion of all the reasearch done do far.

So, it seems, that it is simply not possible to use any incremental update available right now with the current (4.0.3 and most likely 4.0.4 too) stock recovery.

Regarding to:

There is however a way that has been reported to work: (starting from a locked, unrooted 4.0.3 with stock recovery)

As full ROMs work fine, flash to 2.3.6 using a full ROM provided here: http://xdaforums.com/showthread.php?t=1063664

Reboot right back into the recovery (Booting into 2.3.6 might mess up something)

Flash a 4.0.3 (full or incremental, it shouldn't matter)

Flash the 4.0.3 -> 4.0.4 incremental (this works because we are still in the recovery that came with 2.3.6)

Reboot

Have fun with 4.0.4

The reason why an incremental update in the 4.0.3 recovery fails is still unknown.

No evidence that this may be on purpose has been found so far.

There is a lot of source yet to be used to find this out. ;-)

Just summing up what already has been posted with some explanations.
[Nexus S General] heilmaenner:
Do I lose my installed Apps (=Wipe) if I flash back to 2.3.6 and then to 4.0.3 and .4?
[Nexus S General] DarkhShadow:
Maybe, but do a backup then just try it

Sent from my ice cream powered Nexus S
[Nexus S General] qorron:
no, you do not.

apps and stuff are in /data and this is not touched by the update process.

(4.0.4 "optimizes" the apps at the first boot, but nothing was lost in my case)

however:

there may be a reason to wipe after the update e.g. if the system fails to boot (this is not expected to happen, but who knows..)

so, a backup of some sort is always recommended.
[Nexus S General] heilmaenner:
Okay. But since my bootloader is still locked and the phone is unrooted, I will not be able to downgrade from 4.0.3 to 2.3.6, right?
[Nexus S General] eddiem74:
Anyone? :p
[Nexus S General] DarkhShadow:
Unless you get OTA then yes

Sent from my ice cream powered Nexus S
[Nexus S General] Hyst3RiA:
Link YouTube : Nexus S with official ICS 4.0.4. It's very fast :cool:

http://www.youtube.com/watch?v=dPRI...DvjVQa1PpcFPuWinLN3G9sPpltPkfARId3QBr4-a976s=
[Nexus S General] explorer-10:
How can you tell if the update from gb to ICS is full or incremental?
[Nexus S General] oldblue910:
If you're running 2.3.6 it'll be incremental. If you're running 2.3.4 or earlier, it'll be a full ROM package.
[Nexus S General] crazychubchub:
Updated from 4.0.3, rooted.

Works great, can´t say whether 4.0.4 is better/smoother that 4.0.3 because 4.0.3 was already good, but thank you for the link!

Edit: Display flickering after updating.
[Nexus S General] nolook:
finally got this update to work on my AWS I9020 4.0.3 nexus *without* having to wipe the system....this is very noob friendly and only took 2 mins...found out about this from a post on howardforums...

1. Root using this exploit - you will need usb debugging, sdk, samsung drivers, etc

http://xdaforums.com/showthread.php?p=24249584#post24249584

2. download and run superuser

3. Flash CWM via Rom Manager

4. Flash OTA 4.0.4 update via CWM

First impressions of 4.0.4 is its faster (esp browser) than 4.0.3...
[Nexus S General] Azzabear:
For anyone that's interested in how other devices are forcing the OTA, Wifi Xoom's can force the update by clearing the app data for Google Services Framework, rebooting, then checking for updates. Worked for my Xoom but it doesn't seem to work for my Nexus.

http://xdaforums.com/showthread.php?t=1568682&page=8

Anyone know how to do the equivalent on a Nexus S?
[Nexus S General] mtwkid:
Install 4.0.4 from factory images

Tried to upgrade using hR7QFEtn.zip but got error status 7. Finally I got 4.0.4 installed on my I9023 (locked bootloader; unroot; full stock 4.0.3) by installing factory images.

I did these steps:

- Get "soju" 4.0.4 (IMM76D) factory images from Android.com

- Install Android SDK and Android USB Driver

- Follow instruction from androidtobe.blogspot.com, just replaced commands with what mentioned in flash-all.sh file.

*sorry, i can't post the links because i'm a new member :D

Thanks for the thread!!
[Nexus S General] drmwnhrn:
Hi guys,

I can update to 4.0.4 to my I9023, but can't make it rooted. I tried to flash superuser via CWM but failed after booting.

Is anyone could give me direction how to root properly?

Thanks
[Nexus S General] dbal:
Critical question. After applying the update, does the phone reverts to stock recovery and loses root? Basically that's what I hope for so I can have it in a pure factory state again...
[Nexus S General] m.sabra:
Try my one click root tool (check my signature for link)
[Nexus S General] drmwnhrn:
Thanks anyway, but is there any other way without wiped all data from my NS?

---------- Post added at 03:24 PM ---------- Previous post was at 03:19 PM ----------

I thought so,

after updated to ICS 4.0.4, my device still un-rooted & unable to boot recovery using CWM.
[Nexus S General] m.sabra:
If your bootloader is unlocked it will not wipe your data.
[Nexus S General] oldblue910:
It appears that Google is actually releasing incremental I9020T/I9023 updates for every single version to 4.0.4 this time instead of a full ROM update. Not sure why they're doing this, but here's what we have so far:

2.3.1 -> 4.0.4

2.3.4 -> 4.0.4

2.3.6 -> 4.0.4

4.0.3 -> 4.0.4

I am currently running 2.3/GRH55 to try and get whatever OTA link they put out for that. Would someone be willing to run 2.3.2, 2.3.3 (GRI40) and 2.3.3 (GRI54) and nab those links?
[Nexus S General] gray/fox:
So have you received your update from 2.3/GRH55 to 4.0.4?

I'm currently running GRK39F (2.3.6) so I'd be happy to get the links they send out OTA...I just don't know how :p I've never received an OTA as of yet. If you'd be willing to tell me how to link to the OTA file, like I said I'd be happy to post it :)
[Nexus S General] oldblue910:
No, I haven't got the OTA for GRH55 -> IMM76D yet. Hopefully soon!
[Nexus S General] gray/fox:
Fingers crossed! I've got a UK i9020 sim free, but am living in Spain so I have no idea how long it'll take for the update to roll around here.

Do you know how I can post the link once I receive an OTA update?
[Nexus S General] oldblue910:
Turn on USB debugging on your phone (in Settings | Applications)

Install aLogCat from the market.

When you get the OTA notification on your phone, don't reboot or do anything else on your phone. Instead go straight into aLogCat, and do a filter on ".cli" (without the quotes) and you should find the link to the .zip file in there.
[Nexus S General] nolook:
yes it does loose root...and the exploit doesnt work on 4.0.4 so you can just run it again...i actually wanted to keep root but now have a stock 4.0.4. i will just wait until there is another exploit to get root (without wiping!)

not sure about recovery but i assume that would be stock too now at this point...
[Nexus S General] oldblue910:
Yes it does. You will have stock recovery and will lose root.
[Nexus S General] Flash05:
Hey there! THanks for the instructions and link! I upgraded my Nexus S to 4.0.4 already.

I just have one tip to those who plan to use this step - touch recovery is sensitive. i wiped my phone :( i should have opted for the non-touch.

still +1 to you sir! :):):)
[Nexus S General] gray/fox:
For everyone else having trouble, and not wanting to upgrade from 2.3.6 >> 4.0.3 then from 4.0.3. to 4.0.4, oldblue910 has posted most of the updates from i9020T on this page:http://xdaforums.com/showthread.php?t=1445570

I went from 2.3.6 straight to 4.0.4 with the .zip, with stock recovery, unrooted (i.e. I made no changes to my phone since buying it last december) and the update was perfect.

It was as simple as renaming the rom to update.zip, opening the recovery during a reboot, and selecting the file from my sd card.

Since everyone is having trouble from 4.0.3 to 4.0.4 I would recommend this method greatly. :)
[Nexus S General] Lazer Bear:
Agree and can vouch for this method as well.. Had absolutely zero problems, all my apps work perfectly and phone is very smooth!
[Nexus S General] ctai320:
I really want to try this so thanks for the post and for the verification. but I heard that doing a wipe is much better when upgrading. Even my gb has been starting to lag like crazy recently. Wondering if clearing davik and system cache will help. Or when upgrading through this method, will all of these automatically reset? I'm completely stock with locked bootloader. Sorry for the noob question.
[Nexus S General] gray/fox:
From personal experience with my old phone when applying cyanogen mod etc. I had always cleared the caches and wiped my phone, however I actually forgot to do this before applying the 4.0.4 update.

In my opinion, I don't really see a huge difference it could make to my nexus s, because 4.0.4 runs smooth, I mean really smooth. Smoother than GB. I guess there wouldn't be any harm in wiping your phone if you have a lot of data stored on there, or apps etc.

No need to apologise either haha, I'm kinda a noob myself so don't worry, one thing I don't really understand is the whole 'locked bootloader' business? What do you mean? I'm from the UK so they sell the nexus s unbranded sim free anyway, so does that mean my bootloader is unlocked, whereas those who have bought it via a carrier, e.g. Sprint, Verizon, T-Mobile.... have their recovery/bootloader locked?
[Nexus S General] chapman2109:
2.3.6 to 4.0.4

Hi! I've just registered to XDA just to post this.

I just received my 4.0.4 update from 2.3.6 on my UK i9020

I've got the link using oldblue910's instructions on the previous page. Here it is:

hxxp://android.clients.google.com/packages/ota/google_crespo/fL9fwa99.zip

Hope this helps! :D
[Nexus S General] thecraigmcrae:
I'm getting random restarts and the lock screen becoming unresponsive with this.
[Nexus S General] panther-'black':
Great!
[Nexus S General] hulkamaphone:
I can confirm recent posts about clearing the cache in google services framework and re-trying the check update. It worked for me first try after bothering about with the manual download and shining a torch on the lcd to see the writing.

Update was with Telstra (Australia) pre-paid.
[Nexus S General] majestik666:
clear data worked for me too

well I tried many times to clear data then check for update but nothing ..

but clear data -> reboot -> check for update => worked on first try !

EDIT : also noticed during the download of the 17MN update , the screen mentioned

Wifi Only until Apr 11

not quite sure what that means or refers to...
[Nexus S General] bmeagle:
My wife's at&t nexus s just got the ota update after I cleared google services and booted the phone, stock 2.3.6 to 4.0.4. We're in south africa, but that shouldn't matter with a nexus phone.
[Nexus S General] traktori:
Just have to confirm, clearing data from Settings > Apps > ALL > Google Services Framework, does the trick even without reboot :)

I got the update, phone restarted and screen went black for couple of minutes after which I got 4.0.4 final reboot. No errors, all working fine.

Had 4.0.3, unlocked bootloader, not rooted 9023.
[Nexus S General] d3one:
omg

battery died after 6 hrs 52% takes android os my version is 4.0.4 i got it via OTA ! wtf ?? google didnt fixed it?

http://imageshack.us/photo/my-images/838/shot000001m.png/
[Nexus S General] DarkhShadow:
You mean 11 hours? And 47%?

Sent from my ice cream powered Nexus S
[Nexus S General] d3one:
Yes it was 52%

I need to do factory reset?
[Nexus S General] Lazer Bear:
I had your same problem, usually can be solved w/o resets. Try the following methods in this order: 1) turn off your phone, then turn on again. Use normally for a while and check if the OS % goes down. If not, 2) delete ALL widgets from all your launchers. Use normally and check OS. If solved, you can put widgets again. If not, 3) use a custom kernel.

n.2 did the trick for me, hope you can solve it as well..
[Nexus S General] Davrat:
Same experience for me, stock 4.0.3, cleared the framework just once, went to phone info clicked check for update and it all went swimmingly. Definitely smoother than 4.0.3 no long lags going back to home, even Tapatalk seems faster!
[Nexus S General] deviantartjr:
Still waiting for my nexus s, I'm using stock 4.0.3
[Nexus S General] atirage:
Thanks for the tip, but I needed too the restart and then the check for the update.
[Nexus S General] whatever69:
Just received OTA update for 4.0.4

Hi,

First time poster, long time reader :) I have 2 Google Nexus S phones on Wind Mobile:

Mine was at 4.0.3

My wife's was at 2.3.6

Mine simply updated on it's own. For my wife's (2.3.6), I used the above mentioned trick of clearing the data for Google Services. I rebooted, and by the time I went to "About Phone" it was already downloading 4.0.4. I was just impatient. I turned on WiFi on both to download faster.

Both went well.
[Nexus S General] Poejie:
update 4.0.4

work Great on My i9023 :) No data loss, Flash manually from CWM and then reboot. stock recovery not work but it doesn't matter I flash CWM recovery via fastboot,
[Nexus S General] mooz1:
I have rooted Nexus S 3G. Got the 4.0.4 update and it is still sitting in cache. Now and then I get the popup to update and get the option to Install Now or Install latter. When I select Install Now and try to update the update fails , I get

and the phone freezs. I have to take out the battery to unfreez ( if there is any word like that ) it.

I googled the problem and found this

Update: It looks like updates on Nexus devices without SD cards can not be performed manually unless you either root or use a custom recovery, like CWM - otherwise, you'll get the errors many of you are seeing. It seems to be happening because the OTA files check whether they're located in /cache, which isn't writable unless you root or receive a proper OTA. JBQ himself confirmed it, but said it wasn't on purpose. The preferred solution seems to be using a custom recovery, then installing the above update. Galaxy Nexus has a similar problem, so you're not alone.

http://www.androidpolice.com/2012/03...-it-right-now/

There you have it. I got the update and can't do anything with it.
[Nexus S General] DarkhShadow:
Your rooted, you need to unroot to do OTA

Oh and you can't manually update on ics recoveries, that's all

Sent from my ice cream powered Nexus S
[Nexus S General] mooz1:
Dark Shadow following your advice I unrooted my nexus s 3G following this video

http://www.youtube.com/watch?v=cdo8xfr-FvY

The video is for 4G and it returns the phone to stock android 2.3.4. Mine was 2.3.6

Now the problem: I have no network connection. Emergency call only. My network type was WCDMAonly. After unrooting when I try to select WCDMAonly it wouldn't select. The network type is stuck at UNKNOWN and can't change it to anything else.

Any solutions other than running to Mobilicity (my network) ?
[Nexus S General] mooz1:
Help please