yashsingh1/xdaforums huggingface dataset:
[Nexus S General] Jonathon Grigg:
If all you have done is to root your phone, then the update should still come automatically OTA as it always has. The only thing is that the update will break root until you re-root it again.

If you have installed a custom rom such as CM7 or MoDaCo etc then you will have to wait for the developers of those roms to release an update which you would flash with Clockwork Recovery.
[Nexus S General] ripperrs:
ok thanks!!! :D
[Nexus S General] AtomicPC:
What does fastboot oem unlock actually wipe? Just sd? Or will it revert my phone back to 2.3?

Atomic
[Nexus S General] Jonathon Grigg:
I believe it wipes everything on the phone and then restores it to factory condition (not sure if it would be 2.3 or the last version you had ie 2.3.2). Of course its not factory condition because the bootloader is unlocked but there's nothing left on there.
[Nexus S General] AtomicPC:
Well my boot loader is still locked. I updated, lost root... But before I did a backup from fastboot boot crespo also titanium and copied my sd.

Atomic
[Nexus S General] AtomicPC:
Okay, I was able to get back to my PC and ran the fastboot oem unlock on my phone. It brought it down to an out of the box 2.3.3. So that answers that question.
[Nexus S General] CB620:
Update To 2.3.3 And Keep Root Easiest Way

if you have clockwork mod use this as a restore and you will have a rooted 2.3.3 its the easiest way to do it.

http://www.mediafire.com/?c1ww7zb837uycbk

just unzip and put the backup folder in your clockworkmod recovery folder boot into recovery and restore 2.3.3 takes 2 minutes and you will boot up with a rooted 2.3.3
[Nexus S General] islammanjurul:
so can it carrier unlock my phone and make it useable abroad or any gsm/2.5G/3G carrier worldwide?
[Nexus S General] Jonathon Grigg:
Unless you obtained your Nexus S through Vodafone (I think they are locked, not sure though) then your Nexus S is already carrier unlocked out of the box, no messing around required. As long as the carrier uses the frequencies supported by the NS then just pop in your SIM card and go (:
[Nexus S General] amjad_2020:
i try this way with the last Firmware i9020xxkb3 but dont work

[*** url removed ***] forum rules, no linking to site that requires sign up

oops i forgot to make system mount
[Nexus S General] hkt03:
used this guide to root my nexus s.. thanks a ton!

I've searched around a bit but is there any need/use to keep the stock recovery on the phone instead of renaming the one file in order to make CWM stick?
[Nexus S General] AllGamer:
only if you plan to return the phone for repair/service/exchange or resale

else stick with CW recovery ;)
[Nexus S General] hkt03:
Great, thanks
[Nexus S General] distortedloop:
AllGamer-

Since your method should work on 2.3.3 as well, perhaps rename the thread to include GRI40 in the title? Someone indicated reluctance to try this method on 2.3.3 since the thread says GRH78.
[Nexus S General] AllGamer:
done, updated.

yes it does work with all versions
[Nexus S General] Ahmun_Ra:
I've done this once and had worked perfectly, but i installed the 2.3.3 and all of a sudden i don't have recovery mode anymore. Tried to do it all over again and no luck. Can't install SU " An error occured while attempting to run privileged commands". This is what it appears every time i try to install any zip.

Help please
[Nexus S General] AllGamer:
after installing 2.3.3 it re-enables the install.sh which severs the link to the CW recover, and points it back to the original recovery

all you need to do is repeat the process from the part where you fastboot the image file to the ROM
[Nexus S General] Ahmun_Ra:
Done that and when i open the recovery on the fastboot menu goes to the original. Can't get it :(
[Nexus S General] AllGamer:
did you do the rename step on message #2?

http://xdaforums.com/showpost.php?p=10238348&postcount=2
[Nexus S General] islammanjurul:
I will be buying my nexus s from t-mobile USA for 530 bucks without contract, best buy says it is still locked even without contract.. so how to unlock that nexus s?
[Nexus S General] AllGamer:
Bestbuy is BSing you... Nexus S are not SIM locked
[Nexus S General] benrees21:
Allgamer thanks for your guide, worked a treat on 2.3.3. You might wanna add, that in the Android SDK you have to copy 2 DLL files to the tools folder (well I did anyway). Thanks again.
[Nexus S General] AllGamer:
it's in post #2 already http://xdaforums.com/showpost.php?p=10238348&postcount=2

people seems to just keep missing it :p
[Nexus S General] benrees21:
Oh sorry mate. Yea I missed it lol. Thanks for this though, nice of you to make it easy for first timers.
[Nexus S General] mac227:
Should I update my NS to 2.3.3 before I try to root it, or is it ok to leave in on 2.3.1?

Also is it true that rooting the phone makes it faster? And are there any disadvantages to rooting the phone?
[Nexus S General] AllGamer:
it makes no difference which version you root.

the sooner the better, because when you root, you lose everything, and need to start from scratch

so it's best to root as soon as you get the phone

there is NO WARRANTY issue, people have submitted their phone for warranty rooted without any complain

no rooting does not make your phone faster, it's the hacks, optimizations, modifications and speed improvements that makes it faster
[Nexus S General] atomikpt:
Allgamer thanks for the guide.

But I have a question:

Does this unlock works for SIM cards like Vodafone Nexus S (that is locked to vodafone users only) ?

Or is it need anything else? Is it possible?

Best regards.
[Nexus S General] AllGamer:
Nexus S are not SIM locked from factory, there is no need to unlock the phones

this guide is only for ROOTing the phone
[Nexus S General] mac227:
If I were to root the NS and Android 2.4 come out (ice cream) how would that work as far as updating my NS? Would it screw up any modifications I have made or would I be unable to update or anything like that?
[Nexus S General] Alopez_45:
So after trying everything that I can. When I'm in the command prompt I type n fastboot oem unlock. still nothing seems to work. It says that it is waiting for device is there something that I am missing.
[Nexus S General] zorak950:
I'm having a problem, and I'm not really sure where to ask for help, so I'll try here and hopefully someone can at least point me in the right direction.

I'm trying to install the PC software, and I've gotten stuck. I installed the SDK, but I was unable to install any of the packages, including the one I need for this procedure. I searched this thread and gathered that I need to install the other programs, but when I download Eclipse Classic, it won't start because it can't find my Java installation path. All I really want to do is root, and this seems to be getting very complicated. Any pointers on getting things set up PC-side?
[Nexus S General] tatwamasi:
Fastboot wasn't part of my SDK download so when I try to run it in Terminal (mac) nothing happens. I can't work out where to download it from, 2.3 is no longer available and it doesn't seem to come with the 2.3.3 revision.

Unless I'm being silly.

EDIT: Managed to find it included with Modaco's Superboot:

http://android.modaco.com/content/g...-colour-revert-superboot-rooting-the-nexus-s/
[Nexus S General] AtomicPC:
If you have PDANet installed on your computer and it's running, it will give this error. Stop PDANet from running on your computer before you go into fastboot mode on your phone.
[Nexus S General] Simer03:
thanks so much for this!!!!
[Nexus S General] rellivisit:
edit: problem solved
[Nexus S General] distortedloop:
Root in and of itself has not been an issue on the 2 previous OTA updates, the only issue was people lost root and had to re-root.

Where people run into trouble in the terms of your question is rooting the phone and then installing custom kernels or modifying stock files that are on the /system partitions. Such modifications include replacing the wifi driver like most kernels do, de-odexing the /system/apps, theming the phone, replacing stock apps like Gmail or Market with modded ones, etc. What happens is the update script pukes and fails when it tries to verify the phone's state. This is actually a good thing because you don't want the OTA to try to patch something that's different than its patch routines were written for.

It's easy enough to get around this. There are several things you can do, and they're discussed in multiple threads in the general and Q&a section that are related to the 2.3.3 update and links.
[Nexus S General] HowlinMadMurdoc:
Ok so I am experiencing a problem with connecting to my phone with fastboot.

I have a Nexus S which seems to be running a custom or developer build, currently marked as Android Version 2.4

drivers are successfully installed on windows xp but when I try to do "fastboot oem unlock" I just get the message <waiting for devices> and it sits there forever.

here is the kicker, it already says LOCKED STATE - UNLOCKED (got the device like this) but without the option to send the recovery image i am unable to do anything.

also, the device isnt rooted.

if you could provide any help that would be amazing
[Nexus S General] AllGamer:
open Device Manager, and see if there is any question marks or exclamation marks

when it says <waiting for devices>, it means the PC is not seeing the phone connected to it.
[Nexus S General] moordown66:
I’m new to this forum but have been trying to follow this guide to root my Nexus S. I am seeing a similar problem to the one above and I’d really appreciate some help with it as I’ve run out of ideas. This is my first time trying this as I’m a new Android user but I can’t see any reason why this shouldn’t work.

The situation is as follows:

USB debug is on. Phone is in fastboot mode.

I have downloaded SDK, downloaded everything it offered me and have extracted the drivers and they're now fully recognised via device manager as Android ADB Interface. No exclamation marks – it’s there properly.

Next thing I do is open a command prompt and point everything at where my tools folder is (that's c:/androidsdk/tools in my case). That's good, it can see that.

All the fastboot stuff appears to be in the tools folder (the likes of fastboot .exe, adbwinapi.dll etc.) Is that the right place for it?

On the cmd I then type c:\androidsdk\tools>fastboot oem unlock

That's when things grind to a halt. I get the message <waiting for device> which just hangs forever and on a couple of occasions when I've tried (and failed) to unlock it, on a the very bottom of the screen I get the message 'fastboot status FAILInvalid command'....but I don't always get that. I’ve tried this about 10 times now but don’t always get the FAILInvalid message – sometimes nothing.

The other info on the screen is as follows:

Fastboot mode (it's in red)

Product name - herring

HW version - rev11

Bootloader version - I9020XXJK1

Bootloader build - Nov 4 2010

Baseband version - I9020XXJK8

Serial number - (it's on there - won't put it on here)

Lock state – locked

I haven’t been selecting any of the options with the vol up/vol down button & power, just leaving it exactly as it is when I enter fastboot mode. Should I have been doing something different there maybe?

So....I've obviously done something wrong. Am I missing something glaringly obvious or have I missed a step? Does this give anyone any clues what it might be, and and any chance of explaining to me how to put it right so I can get that bootloader unlocked and the thing rooted?

Starting to get really mad with it now and would really REALLY appreciate some help!
[Nexus S General] Jonathon Grigg:
It appears to be a driver issue with the 'waiting for device' error. Try installing PDAnet, as it has it's own drivers which seem to work well. Just make sure PDAnet isn't running in your taskbar when you run fastboot.

PDAnet can be found here: http://www.junefabrics.com/android/download.php
[Nexus S General] moordown66:
Thanks a lot for that.

I’d read about PDA net and installed it to my PC. What happened when I installed it (and the phone was connected and in fastboot mode at the time) was a message which said something like ‘installing pdanet on phone’. This just hung and I had to cntrl-alt-del to get out of it.

I haven’t been able to find a guide (that could be me not looking properly) which tells me what I’m actually supposed to do with it. So……

1.	Is there an idiots step by step guide I could use for pdanet?

2.	At which point in the procedure on this thread would I jump in and use pdanet?

3.	How do I use it in conjunction etc etc etc.

As I said, this is where I’m getting confused because due to being new I don’t know what to use or when and where.
[Nexus S General] Jonathon Grigg:
A while back I wrote a full on guide based on AllGamer's one here, which you can find here if you need the full version: http://completeandroid.wordpress.com/2011/01/31/complete-guide-to-rooting-the-nexus-s/

Basically the step you are looking for is this:

You shouldn't need to install anything on your phone at this point, select no if you can (I can't quite remember). Maybe even just leave the phone unconnected, unless you absolutely need to (it has been a while...).

This should be done after all the USB Debugging stuff is done on your phone, but before attempting the fastboot oem unlock command.

Good luck! Just ask for any more help if you need it :D
[Nexus S General] moordown66:
Thanks. Will get onto that tonight, but don't be too shocked if I have more questions :rolleyes:
[Nexus S General] moordown66:
Actually, I've got one question already....

We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.

Do I have to do anything to get the driver to install. I'm assuming I just install pdanet and everything else happens automatically after I click Samsung or is that a wrong assumption? I'm sure after that step when I tried yesterday it tried to install itself on the phone and crashed. I'm pretty sure it did that automatically and didn't give me an option not to do that (or install drivers either).
[Nexus S General] Jonathon Grigg:
I can't remember off the top of my head, but maybe check and see if there is an advanced mode or something.

Sent from my Nexus S
[Nexus S General] moordown66:
There definitely seems to be some sort of communication problem with the phone.

I've followed steps 1-10 of part one of the guide you linked to above to the letter.

On Step 2 I've got stuck on step 1. This is what has happened.

I installed pdanet. I selected Samsung. I allowed the driver to be installed. The pdanet display shows the following....

Additional setups

Installing usb driver (ticked in green)

Setting up broadband driver (ticked in green)

Installing pdanet to your phone......

It's just hung at that last one for a good 30 minutes now. Back, next and cancel buttons are all greyed out.

There was no option given to me for an advanced mode or anything like that.

pdanet setup is shown as running ok in the pc task manager.

I'm guessing this is why I'm having some problems. I'm running windows 7 32-bit by the way but I don't think it's the pc end.

Does this spark any further thoughts or ideas with you Jonathon (or anyone else?)
[Nexus S General] Jonathon Grigg:
Well when I get time today I will try installing PDAnet on my lappy again and see what the steps are for you. Just a quick thought, if your stuck at the phone setup part, is your phone on? Just trying to think of what could go wrong that's all.

Sent from my Nexus S
[Nexus S General] moordown66:
It's on in fastboot mode (vol up & power on).

Had a sort of half theory that the win7 pc wasn't allowing the necessary permissions or something so I dug out an old XP laptop and repeated the process and got to exactly the same point and had exactly the same problem. For me, that was good enough to suggest that the problem could well be at the phone end.

In case it was something I had on the phone causing a conflict or something I did a factory reset (after all, I was going to wipe everything anyway) and tried again. Same result.

Assuming my theory is right, what on the phone could be preventing the connection? Or is there a chance that it's a version thing on pdanet? <Thinking aloud now> the drivers were loaded via sdk and the phone wouldn't connect and pda couldn't talk to the phone. Which leads me back to the phone again. What could be preventing it from connecting? Am I missing a step (don't think so) or is there something else going on there?

Tried a different usb cable too by the way.

Wish there was a 'somewhere between totally baffled & furious to the point of throwing the lot out of the window' smiley I could put on now!
[Nexus S General] Jonathon Grigg:
Steps that work on my computer for installing PDAnet, with phone disconnected:

1. Double click on PDAnet installation file

2. Accept any UAC prompts you get

3. Next to continue

4. Accept and next

5. Next (minimum req.)

6. Choose installation folder, Next

7. Wait for it to extract files

8. 'An existing Android USB driver is found on your computer, you can reinstall it if it has problems.' Click Yes

9. Select Samsung as the manufacturer and then OK

10. Wait for the driver to install

11. Click 'Install this driver software anyway' in the Windows security prompt that comes up

12. Turn on USB debugging on your phone, connect it via USB

13. Click OK to any further messages

14. Hit Finish :D

Now find the PDAnet icon in the taskbar and right click, Exit.

[Optional] Uninstall the PDAnet app on your phone if you don't want it

Try using fastboot oem unlock :D

Hope that helps!
[Nexus S General] distortedloop:
Are you able to get adb to recognize the phone if you let the phone boot normally?

Turn on USB debugging mode (under the settings, applications menu), then plug the phone into your computer's usb port, open a terminal shell on the computer, navigate to the sdk folder with the adb executable in it and type "adb devices" into the terminal.

This will tell us if your issue is with fastboot mode only or not.

Also, some Galaxy S models have been notorious for not playing nicely with usb and have required repeated plugging/unplugging of the usb cable to get them talking to the computer. Perhaps your Nexus S is having similar issues.

One other thing you could try is getting Odin from the Dev section and putting the phone into DL mode then seeing if Odin can talk to it (you should see the phone available as a com port in Odin). Don't do anything with Odin, this would just be a device driver test.
[Nexus S General] moordown66:
Thanks for the responses.

Pdanet one first.

@Jonathon

I installed it with the phone unplugged as instructed. Set it to load the usb driver as instructed. I realised that I had previously been doing that in fastboot mode, not in 'normal' mode with usb debugging on. So I did it properly and pda net loaded the drivers perfectly.

So far so good. Booted into fastboot mode, pulled up the command prompt, pointed it at the tools folder, typed fastboot oem unlock.........

<waiting for device>

So - the same problem in other words.

@distortedloop - going to show a stunnig lack of knowledge here:

<Are you able to get adb to recognize the phone if you let the phone boot normally?>

What do I need to do and how do I tell?

<Turn on USB debugging mode (under the settings, applications menu), then plug the phone into your computer's usb port, open a terminal shell on the computer, navigate to the sdk folder with the adb executable in it and type "adb devices" into the terminal.>

Apart from the turning on usb debugging mode bit (I can do that) how do I do the rest? Assume no knowledge at all! I mean, absolutely none!!!

<Also, some Galaxy S models have been notorious for not playing nicely with usb and have required repeated plugging/unplugging of the usb cable to get them talking to the computer. Perhaps your Nexus S is having similar issues.>

It seems to see it ok. I think.

<One other thing you could try is getting Odin from the Dev section and putting the phone into DL mode then seeing if Odin can talk to it (you should see the phone available as a com port in Odin). Don't do anything with Odin, this would just be a device driver test.>

Nah, really lost me now!!!!! :D:confused:

Getting to the point where I'd happily pay someone to do it for me!
[Nexus S General] zadnica:
Link to recovery-clockwork-3.0.0.5-crespo.img is broken.
[Nexus S General] Jonathon Grigg:
http://db.tt/zgRxyTs

I uploaded my recovery-clockwork-3.0.0.5-crespo.img to dropbox a while back after a similar issue. All that is different is I renamed it to recovery.img for the sake of my tutorial when I wrote it ;)

Sent from my Nexus S
[Nexus S General] Jonathon Grigg:
I didn't feel like quoting such a large piece of text, so this is still for the fastboot issue.

Now I'm thinking maybe your phone isn't showing up to the computer at all, so I'm not sure if there is a command like this for fastboot:

fastboot devices

If it lists a device, even if its just numbers and letters then its recognized but if not then there's your problem.

(I got the devices idea from: 'adb devices' but correct me if I'm wrong)

Sent from my Nexus S
[Nexus S General] distortedloop:
Yes, fastboot devices is a legitimate command and should return device serial number.

You can see all the valid adb or fastboot commands by just typing the command with nothing after it:

MBP1:adb-fastboot dave$ ./fastboot
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
[B]devices list all connected devices[/B]
reboot reboot device normally
reboot-bootloader reboot device into bootloader

options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
[Nexus S General] distortedloop:
Well, it seems you know enough to get to and run the fastboot command, so basically all you're going to do is run the adb command instead of fastboot. So it's "adb devices".

The only difference is that you're going to try it while the phone is booted normally into the normal operating system...NOT from fastboot mode.
[Nexus S General] moordown66:
<Well, it seems you know enough to get to and run the fastboot command, so basically all you're going to do is run the adb command instead of fastboot. So it's "adb devices". The only difference is that you're going to try it while the phone is booted normally into the normal operating system...NOT from fastboot mode.>

I don't really know how to run command prompts. I know how to cd to, err, cd and that's all. All I know is using info taken from guides

What needs to go in front of the adb devices command? If I put in this....

C:\Users\moordown66>adb devices

it returns a message saying 'abd is not recognised as an internal or external command, operable program or batch file'.

I'm pretty confident from that message that I haven't put it the command in correctly. How should it be?
[Nexus S General] Jonathon Grigg:
You need to be in your adb directory of android-sdk. I moved across the adb files from platform-tools into tools on my installation, as it says in my guide if you followed it.

Basically enter this (adjusted for your directories etc)

cd c:\android-sdk-windows\tools

adb devices

Sent from my Nexus S
[Nexus S General] moordown66:
Same. adb is not recognised as internal or external command.

And I'm doing this in normal mode, not fastboot mode as instructed in the earlier post, right?

This is the same in normal mode or fastboot mode. Can't believe I'm so useless at this. Normally get things to work ok