yashsingh1/xdaforums huggingface dataset:
[Nexus S General] jonc:
He's already installed it (as I said). So too late for that. Hence my question.
[Nexus S General] jonc:
Whereabouts would the cache be?
[Nexus S General] black beard:
There is no way to grab the URL after the update has been applied as the update reboots the device and the log data is wiped.

The log data has to be exported after the update notification has been received, but before the update is downloaded / applied.

If your "friend has the update", then its too late. And without evidence you run the risk of being accused of being a troll.
[Nexus S General] jonc:
Pants. I suspected as much. He's not as techy as me/doesn't frequent XDA-dev, so didn't occur to him that he might be able to help us out.

I can't provide any evidence per-se, I can say that he works for google, so it's possible his gets pushed out before consumer models (he has one of the ones with the little android logos on the battery cover). I'll see if I can get the baseband/kernel/build numbers.
[Nexus S General] antz88c:
Simple, post pick or it didn't happen.
[Nexus S General] moon-unit:
So far from reading this forum and the same thread in the Nexus One forum the only people to have received the update are Google employee's, I think Google are being very careful with this roll out and are using there own staff to be sure neither the NS or the N1 are not going to be bricked or suffer any unexpected bugs in 2.3.3.

I think it could take a while for the OTA to reach Joe public.......

A google Employee on the N1 forums posted a picture:

http://xdaforums.com/attachment.php?attachmentid=526082&d=1298547707
[Nexus S General] shrivelfig:
Don't remember, but /cache might be a start ... :p

Well, some (desperate) solutions are:

- Full backup, then restore an earlier OS and try again

- Editing /system/build.prop to pretend to be 2.3.2
[Nexus S General] rzaratin:
No download link yet??

Any news about CM7 update?
[Nexus S General] nyusika:
...post from google issues...

Yesterday (19 hours ago)

I'm using a Google holiday Nexus-S.

This morning, I recieved an OTA to 2.3.3, build number GRI40, Kernel 2.6.35.7-g1d030a7, android-build@apa28 #1, baseband I9020XXKB1.

Before the OTA, everything was working correctly. After the OTA, the back button has stopped working.

I've got the vibration on keypress turned on. The other three hardware buttons (menu, search, and home) all continue to work correctly, and the phone vibrates when they're pressed. The back button doesn't respond at all - not even to vibrate on press.

This seems to be true in all contexts - the home screen, inside preferences, and in every application that I've found that uses the back button.

To reproduce, I would guess just do the OTA upgrade, except that I'd guess it would have been seen before.
[Nexus S General] tommy.snello:
hxxp://twitter.com/#!/googlenexus/status/40221838743179264

Gingerbread (Android 2.3.3) update now rolling out to Nexus S and Nexus One. Be patient, may take a few weeks for OTA to complete.
[Nexus S General] benrees21:
Now i have had no issues with my NS apart from the gallery lagging out now and again but if this issue rears it's head after the update then im gonna be pissed!
[Nexus S General] jalyn02:
How about a screen shot huh? Nobody has the update as of yet.
[Nexus S General] amjad_2020:
if the bootloader will be close we can use Odin from Download Mode ...........

http://xdaforums.com/showthread.php?t=947950&highlight=Odin
[Nexus S General] krohnjw:
The bootloader will still be able to be unlocked/locked using fastboot. The only change noted in the changelog is that they are not allowing fastboot boot boot.img (useful for booting a custom recovery) when the bootloader remains *locked*. This was the method of rooting (boot CWM and flash the SU binary) without unlocking the bootloader. As this is clearly not how they intended it to work, that's being patched up.
[Nexus S General] distortedloop:
You are spreading FUD; please check your facts before posting.

You do not (currently) need to unlock the bootloader to fastboot FLASH a recovery image. A dozen or more people have reported successfully flashing clockwork via fastboot and rooting their phones by using the method in this thread which does not have you do the fastboot oem unlock command (ie., unlock the bootloader).

I think we shouldn't panic and spread hysteria around here by making the assumption that disabling the fastboot boot command while locked also disables the fastboot flash command. If it did, wouldn't Google have mentioned that in the changelog?

It may indeed be a problem in the future, but until the code is out, it's pure speculation either way.

You don't know that for a fact. Calm down and wait for the update to actually hit, then we'll see.
[Nexus S General] NVMENOR:
krohnjw is right, Bootloader won’t have substantial changes, you still have the option to unlock it in order to use “boot” and “flash” commands, and as long as fastboot is working, I wouldn't use Odin, I consider it as the last recourse before sending the device to Samsung service.
[Nexus S General] Rusty!:
WHOOP! WHOOP!

That's the sound of the irony alarm.

If you actually read that thread, you would see that the command fastboot flash is not being used. The command in question is fastboot boot, and that is what is being disabled.

Again I state: fastboot flash will not work with a locked bootloader.
[Nexus S General] distortedloop:
Whoop whoop....if you check that thread, you'll see I am the one who wrote it....talk about irony.

Also, if you check this post specifically from that thread, you'll see I mention this might be a security hole Google will try to patch some day.
[Nexus S General] Rusty!:
So let me get this straight, you wrote a thread stating you can fastboot boot a new recovery (something that is not in dispute here) and use that as evidence you can fastboot flash a new recovery with a locked bootloader?

Goddamn :rolleyes:
[Nexus S General] grippa:
LOL

if google we're doing a mind experiment to frustrate people, then this is it.

over 15 pages of frustration and now we're on about alleged 'fastboot' locks and what not - we all know that whatever locks will be eventually broken. plus this is one of the 'suggested' phones for google developers, so I doubt they'll make it that hard to root/flash new roms.
[Nexus S General] shrivelfig:
Whoop whoop ... :p

Anyhoo, I wonder if it will be possible to re-flash the old bootloader after updating. I think I will do some experiments when Google finally manages to start cranking out the OTA to the unwashed masses.

You hear me, Google? Just give us the gosh-darned download link already!
[Nexus S General] distortedloop:
No I am pointing out that the fastboot boot command is not the same thing as the fastboot flash command. You roll your eyes in some sort of pedantic superiority complex, but you've yet to post any evidence that your assumption that disabling fastboot boot in the next update will disable other fastboot commands is accurate. Can you reference something that shows this is fact, or is it just something you've assumed?

There are numerous different fastboot commands. Only one of them is mentioned as being changed. Beyond that change everything else is simply speculation.

This is easy enough to test out. Ask any of the people who currently have locked bootloaders to try the fastboot flash command. There are plenty of folk here who did the oem unlock, rooted their phone, and then relocked the bootloader for some bizarre reason as well as any who skipped that step in the first place.
[Nexus S General] nitsuajd:
Yeah! maybe you're right but i'm in panic mode... :D

I'll Wait for the update and then we'll see....
[Nexus S General] Rusty!:
I don't get this. The stuff you seem to think I am stating, I haven't.

All I've said is that fastboot flash doesn't work on a locked bootloader, and that's how it's going remain.

I've not mentioned disabling anything other than the fastboot boot command when locked, which we all know about because it's been publicised. I've speculated nothing?
[Nexus S General] distortedloop:
Fair enough!

Part of the panic assumptions here seem to be underwritten with the fear that this change will not only disable "fastboot boot" and possibly disable "fastboot flash" on locked bootloaders, but that it will also lock our bootloaders again. Otherwise what's the big deal if you're already unlocked? It's a total non-issue if you're unlocked.

The only concern I would have is that the OTA locks the bootloader and that we'd have to issue the oem unlock command to regain root, and therefore have to WIPE our systems to do it.

With that in mind, it certainly would be a very good idea to do a full Titanium Backup of all your apps and data, then offload the backups to your computer for future use BEFORE letting this OTA install.

If indeed the worst happens and you need to wipe your phone to regain root, at least you have the stuff safely tucked away for restoring after re-rooting.

Personally, I'll wait and see what happens with those who feel compelled to apply the OTA immediately before doing it on my system. No need to be on the bleeding edge for me. YMMV.
[Nexus S General] distortedloop:
You are stating that "fastboot flash" only works on unlocked bootloaders with the Nexus S, and that that will be the case after the OTA. You state it as fact.

I don't know that it is fact because I have not tried it. If you know it as fact, fine, but I'm asking how you know this. Experience, documentation, or assumption?

If experience fine, just say you've tried it and it doesn't work. If documentation, post a link, I'd love to be educated and proven wrong, the lesson sticks better that way. If assumption, than I really don't care to continue the back and forth.

My main concern here is that everyone's getting upset that we're somehow getting screwed when in fact we're not even remotely screwed unless our bootloaders get re-locked with no ability to unlock and regain root available to us. There's no evidence to that, and there's no reason to assume it's a concern. Google's officially stated this phone was designed to be easily rooted and modded; why would they do a 360 at this point?
[Nexus S General] krohnjw:
Seriously, this has gone on for too long. It doesn't work with a locked bootloader. It didn't work on the Nexus One and you guys annoyed me enough to relock and end this discussion on the Nexus S.

fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img

sending 'recovery' (3980 KB)... OKAY [ 0.840s]

writing 'recovery'... FAILED (remote: Bootloader Locked - Use "fastb

oot oem unlock" to Unlock)

finished. total time: 0.842s

(now back to unlock and restore copy everything back to my device >.>)
[Nexus S General] liorry:
Still no link... or system dump :(
[Nexus S General] yellathcir:
"SiddharthSaiG: Can anyone tell me how to convert a nandroid backup into an update.zip? If you can then, 2.3.3 on your nexus."

--http://twitter.com/SiddharthSaiG/status/40795563121188864
[Nexus S General] neu242:
I think he's got the Nexus One, though...
[Nexus S General] CB620:
Agreed.. This topic keeps losing focus where is the link? Our better yet where are the ones that supposedly have the update already
[Nexus S General] benrees21:
If they are pushing this update out then surely someone has it??
[Nexus S General] gusdgg:
I compiled Android 2.3.3 from aosp source for crespo (Nexus S). If it's useful for someone, I could upload system.img, boot.img, recovery.img and userdata.img to a fileshare server.
[Nexus S General] jalyn02:
They are not pushing the update out. I will post the dump/screenshot when the update/ota is finally, really pushed out.
[Nexus S General] shrivelfig:
Well, maybe they're not pushing this update out to everybody yet.

Maybe they're only pushing the update to people that work for Google for now, just to test it some more, to avoid a repeat of the infamous Windows Mobile 7 update.
[Nexus S General] benrees21:
Well they need to hurry up about it. Don't worry if I get it before anyone else (like that will happen) then ill post it.
[Nexus S General] benrees21:
How useful is that tho?
[Nexus S General] unknownkwita:
RFID is a subset of the NFC standard from what ive heard
[Nexus S General] ravidavi:
Other way around ... NFC is a subset of RFID. It simply limits communication to a small physical distance.

Standard RFID is what's used in (for example) wireless toll tags that let you drive through and get charged automatically. NFC is similar to that, just with a distance limit of centimeters instead of decameters or even kilometers.

A good article on NFC vs RFID.
[Nexus S General] n61adm:
So has anyone gotten the update?
[Nexus S General] netninja:
while i'm heartened to hear about 2.3.3 bringing more NFC functionality, I don't think it's going to make any difference i.e. I still won't be able to use it in my daily life.

Unless I'm wrong, if so someone please correct me but I'll only see the benefits of NFC in my nexus s once starbucks, shops and the transit system in my city "actually" implement NFC on their end so it'll work with my nexus s no?
[Nexus S General] zorak950:
It's a bit of a chicken and egg problem. No matter what, it'll most likely be years before the technology becomes truly widespread, assuming all the stars align and NFC is the route that gets taken by mainstream businesses, but enabling the technology on the devices people carry around day-to-day is certainly going to encourage the other side to facilitate that sort of payment. From that perspective, all other things being equal, the more phones get NFC chips- be they Android, iOS, Blackberry, Windows Phone, or just your run-of-the mill dumbphone- the more likely the places you go will become NFC-enabled, and the more quickly they will become so.
[Nexus S General] jivemaster:
I sure hope there is a browser enhancement/fix in there somewhere. Give me epic speed!
[Nexus S General] leyvatron:
The reboot bug SUCKS!
[Nexus S General] unknownkwita:
correct, however now that we can write NFC officialy, there is a good chance that an aplication could allow us to "Emulate" current NFC cards. ie Mifare cards
[Nexus S General] Jayrod1980:
Anyone taking any bets how high these gingerbread builds will go until they get a real finished product? For all intensive purposes it seems this realltly is a Dev phone in that its Google's gingerbread test bed. If this version was actually all patched up to work without the browser and reboot issues I have no doubt the n1 would have 2.3.x at that time. Are any new phones even being slated to release with gingerbread other than the viewsonic with 2.4?
[Nexus S General] mazodude:
stock only. (if you have a custom recovery it won't install, you will have to install manually).

you will have to wait the rom chefs to update for you to get it.
[Nexus S General] zorak950:
Heh. You said "intensive purposes."

>.>
[Nexus S General] antz88c:
Now the waiting begins ...
[Nexus S General] moon-unit:
waiting impatiently for the all important manual download link.........

could be a long few days LOL.
[Nexus S General] jamiemac1977:
If this update fixes my reboot issue, and lets me clone my Oyster card ont othe NFC ... i will forgive them for taking £429.99 off me for a phone that does not yet work as a phone! (properly).

Last device i saw fail so badly at calls was the i-phone4 ... and you would have to kill me to get one of those in my hands.

They have one chance to keep me on android, otherwise its back to maemo and wait! :rolleyes:
[Nexus S General] nardusg:
Don't had the reboot during call issue yet ? That is what makes this issue so irritating...
[Nexus S General] jamiemac1977:
That does seems strange, could be a regional, or paticular production warehouse issue. not sure on the reason to be honest.

All i know is it's pretty sucky to pay that much for something that does not work for it's main intended purpose. If they fix it i'm happy because the phone is freakin awesome!

If not i cannot allow myself to keep it, that would just be asking to be walked over. My aging n900 can do a better job at 1.2ghz ...just the community is sooooo much smaller than here on android (it's a lonely place hehe)

My galaxy tab presuaded me to try a new android handset (my first). not the best first impression ...but forgivable if fixed.
[Nexus S General] ruprick:
I turned NFC on for a few days and noticed pretty significant battery drain. Once I turned it off it was back to acceptable battery life. Anyone else notice a similar trend?
[Nexus S General] Phantom1275:
Anyone already got the update? Links for it, please!
[Nexus S General] onthecouchagain:
I sincerely hope this update includes some major bug fixes.

Attempting to show friends something on my phone, especially a photograph in the gallery, is an invitation for embarrassment. I know it's my imagination, but it feels like the phone is out to get me: it always glitches or has issues, or once even rebooted on its own, at the most inopportune times. And as I said, attempting to show a picture is the worse: I'm usually just standing there for upwards of a minute holding my phone while the albums load, and after they finally load, if the phone really wants to have some fun, it'll sometimes load the wrong photographs.

I've had this discussion with other people before, but if owning a Nexus phone means we're the beta-testers, then I'm not sure how wonderful the Nexus line really is. OEM skins suck in their own ways for sure, but the reality is that stock Android is perfectly capable of hampering user experience just fine by itself. Bug fixes are sorely needed.
[Nexus S General] peakaboohaha:
Crossing fingers on RANDOM ringtone changes in this update... ><

:p
[Nexus S General] :
It's what everybody wants?

Minue the G bits of course.
[Nexus S General] cosimoss:
.... and an official version.
[Nexus S General] j_r0dd:
That would still be incomplete though. There is a new fw_blahblah.bin in the ota we are missing. Check out /device/samsung/crespo/extract-files.sh. it fails to pull one file.
[Nexus S General] krohnjw:
If he's rooted he should be able to edit the build.prop to have a build fingerprint of

ro.build.fingerprint=google/soju/crespo:2.3.1/GRH78/85442:user/release-keys

. A subsequent checking should trigger an update then and the URL could be pulled from the log.
[Nexus S General] elliottn:
still no one has the link?

Not that I am naive enough to think I will have the ota before the link gets out but does anyone know where the link can be found once the notification comes in? I have adb setup (I'm assuming that is needed) on a linux platform and have been able to get bugreport's from my phone. Would the link be there or retrievable using another command?

If i understand the posts previous to this the link must be extracted from the phone prior to downloading and installing the ota
[Nexus S General] krohnjw:
When you get the notification you'll need to run logcat (you can just use adb shell and dump it to a file). Then allow it to download the update. The URL for the update package will be in the logcat output.
[Nexus S General] murdoch1:
Update

Just got all excited then......did a checkin and "updates are available"........turned out to be a bloody twitter update.........damn it........LOL LOL LOL:)
[Nexus S General] benrees21:
Fiendish! !!

Sent from my Nexus S using stock Android 2.3.2 and XDA App.
[Nexus S General] Matrik:
Hi, just did a checkin and the update was there :

[h_t_t_p://]

android.clients.google.com/packages/ota/google_crespo/e0b546c442bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip

sorry for the formattiong, new user, so I don't yet have the right to post links
[Nexus S General] johoja:
IT BEGINS!
[Nexus S General] krohnjw:
Downloading now - well done :)
[Nexus S General] benrees21:
Just go to the URL?

Sent from my Nexus S using stock Android 2.3.2 and XDA App.
[Nexus S General] krohnjw:
Yeah, download the updated - if you are stock place it on the root of /sdcard - otherwise let it download where it does and flash via CWM
[Nexus S General] Azure465:
Great job!
[Nexus S General] slowz3r:
flash from recovery
[Nexus S General] jaker.the.skater:
damn....and i just got it and wanted to post it.

glad someone could post it though!
[Nexus S General] :
I have nothing to offer you but my thanks and my first born :D
[Nexus S General] SupaDupaFly24:
Thank you sooo much!!! Good Job!!
[Nexus S General] laurentbon:
Thank you!!
[Nexus S General] rzaratin:
Applying this will remove root access?

Can anyone confirm?
[Nexus S General] cfhuk:
Yes it will. I'm pretty sure unless anyone else has already updated and still has it. It will flash over some of the system files and remove Superuser.apk from the /system/app folder.
[Nexus S General] krohnjw:
It's going to clear out system and write everything back - so you'll lose root. If your boot loader is locked check here - this is what I did with my Nexus One to keep root after OTAs with a locked boot loader:

http://xdaforums.com/showpost.php?p=11616699&postcount=4
[Nexus S General] krohnjw:
Can anyone running GRH78C successfully apply this - I get a build fingerprint error, says it's expecting GRH78?
[Nexus S General] johoja:
The update is for GRH78, there will be another update package for GRH78C. Will have to wait till someone fishes it out.
[Nexus S General] :
Nexus S: 2

Nexus 1: 0
[Nexus S General] elliottn:
[edit] disregard it appears i am in the same boat as everyone else running GRH78C. This update is not for us. Way to play with our emotions google [/edit]

I am getting an error 7 on my non rooted nexus s during the update. Anyone have any ideas on how to correct?
[Nexus S General] moon-unit:
Nooooooooooo :(

and I thought the wait was over......... :mad:
[Nexus S General] stevea001:
Doesn't work for me, I'm on GRH78C
[Nexus S General] SupaDupaFly24:
So this is for GRH78 only? Bummer I am on GRH78C :-(
[Nexus S General] jaker.the.skater:
dammit i just had it but then it went away and now says my system is up to date. :mad::mad::mad:

ive tried checking in to get it back but no dice
[Nexus S General] leonlmf:
GRH78 nandroid back up is available on this forum maybe someone would like to give it a go
[Nexus S General] cfhuk:
Fingerprint error. It's for GRH78 only by the looks of things. Probably working the phased rollout from the biggest updates needed to the smallest. Probably only going to be a few meg for GRH78C.
[Nexus S General] shrivelfig:
Bwahahaha! :D Sorry, but that's just hilarious!

Now where did I put that stock GRH78 backup ... :cool:
[Nexus S General] krohnjw:
Yeah - I assumed as much. Boo. In case anyone is curious editing the fingerprint to GRH78 won't work - it will fail the check on the system files (boo).
[Nexus S General] rzaratin:
No, my bootloader is not locked, and I'm using CM7RC1 and ClockWorkRecovery.

I will search the root update.zip link to download and apply it after the update.
[Nexus S General] ViLANDER:
Lucky bastards, I'm charging my phone right now! :D
[Nexus S General] nitsuajd:
Maybe can we use a nandroid backup of 2.3.1 for this..

Fastboot boot clockword.img in fastboot mode, and nandroid restore of 2.3.1 version, after this try to install manually... :D
[Nexus S General] cfhuk:
I unrooted and applied the GRH78 Nandroid yesterday to get back to stock so I could get the update. Then updated it to GRH78C thinking that would be the most "stock". Damn. it took me ages to get this thing clean again.

And damn new users having to wait five minutes between posts. Ah well, what we have to put up with for a spam free world.
[Nexus S General] argilo:
Yep, doing a nandroid restore to 2.3.1 then installing the posted update works great. I'm on 2.3.3 now, yay!
[Nexus S General] SupaDupaFly24:
Do you need to be rooted to do a nandroid?
[Nexus S General] krohnjw:
You'll need to have a custom recovery installed.
[Nexus S General] cfhuk:
Nah you can fastboot boot a recovery image and use the nandroid to recover the phone. Remember to put it in sdcard/clockworkmod/backup/ or the "recover from backup" on the recovery image won't find it as a backup file (if you are using clockworkmod recovery).

Edit: you can't flash a nandroid backup like a normal rom. It has to be on the sdcard as a recovery file as if you backed up your own system, and then flashed as such from your installed/booted recovery .