5,604,219 Members 49,394 Now Online
XDA Developers Android and Mobile Development Forum

[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)

Tip us?
 
AllGamer
Old
(Last edited by AllGamer; 8th December 2011 at 09:21 PM.)
#1  
AllGamer's Avatar
Retired Forum Moderator - OP
Thanks Meter 1571
Posts: 11,516
Join Date: May 2008
Location: buried under loads of work IRL

 
DONATE TO ME
Arrow [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)

GRH78
Bootloader v.JK1
Baseband v.JK8

Yes, there are tons of guides out there, and even one click scripts that can ROOT the SNS (Samsung Nexus S) for you, but none of them go into enough detail for any of them to work properly.

Having many android devices working properly via ADB on your computer doesn't automatically guarantees it will see the SNS.

So, before jump to the exiting stuff of ROOTing the SNS, lets cover some basics to actually get you started and make sure you can actually ROOT the SNS, else all is in vain.


MOD EDIT: This guide does not apply to the AT&T/Rogers/Telus variants of the Nexus S (i9020A). For those models, please refer to this guide.
Part 1
  • Download Android SDK release 13 click the file name android-sdk_r13-windows.zip (34 MB) direct from Google, instead of wasting your time jumping through hoops and dodging pop up/flash ADs from those FileSharing places.

    Note: from SDK release 14 onward, Google removed the fastboot command, you'll have to maker the fastboot command yourself if you want to use the latest version of the SDK

  • Turn Off your SNS
  • Make sure the SNS is connected to the PC via the USB cable
  • Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button

  • it reads LOCK STATE - LOCKED
  • open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
  • Do a right click and select Update Driver Software
  • Select Brose my computer for driver software
  • point it to where you downloaded the Android SDK (..\android-sdk-windows\google-usb_driver)
  • Make sure to CLICK "Let me pick from a list of device drivers on my computer"
  • Then from the list 3 choices select Android Bootloader Interface
  • If it's installed properly it should show up like this (reboot is not required)

NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Now that the basic preparations are done, we can finally get to have fun with the SNS & hack away via ADB.exe / FASTBOOT.exe
Part 2
  • open a command prompt go to run & type CMD hit enter
  • switch to the directory where you downloaded & unzipped the ..\android-sdk-windows\tools
  • type fastboot oem unlock and hit enter
  • Then you will get this
  • Code:
    fastboot oem unlock
                                  ...
  • meanwhile on the SNS you'll see this screen
  • selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
  • use the Volume up/down keys to select and Power key to apply
  • you should see something like this after it's done
  • Code:
                                  ... OKAY [435.433s]
    finished. total time: 435.433s
  • now back on this screen you should read
  • LOCK STATE - UNLOCKED
  • Download the clockwork recovery recovery-clockwork-5.0.2.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
  • renamed it to recovery.img
  • then type fastboot flash recovery recovery.img and hit enter
  • you should get something like this, if not your image is corrupted, download it again
  • Code:
      sending 'recovery' (3980 KB)... OKAY [  0.621s]
                writing 'recovery'... OKAY [  0.511s]
    finished. total time: 1.132s
  • Then back on the SNS select Power Off (Reboot also works)
  • Power ON the SNS
  • ...meanwhile the SNS is rebooting Download superuser from http://forum.xda-developers.com/showthread.php?t=682828
  • choose the Eclair/Froyo version
  • Mount the USB storage
    Quote:
    Originally Posted by droidmage View Post
    So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
  • drag/drop the su-version#-signed.zip file into the root of the internal SD of the SNS
  • Power Off the SNS
  • Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
  • select Recovery
  • then it should boot into this screen, if not then repeat the steps to download the image
  • select install ZIP from sdcard (power button to apply)
  • select choose zip from sdcard (power button to apply)
  • select su-version#-signed.zip file you downloaded earlier, and apply it
  • select yes - install su-version#-signed.zip
  • confirm it says "Install from sdcard complete"
  • select go back
  • select reboot
  • done!
Enjoy your unlocked & rooted phone!

Donation is appreciated but not required, a cup of Coffee would suffice

Samsung i9000m: on CM10
Samsung Nexus S: on JB 4.2.2
Samsung Galaxy S II SGH-T989: on CM10
Samsung Galaxy NOTE SGH-i717r: on CM10
Samsung Galaxy NOTE 3 SM-N900W8: stock 4.3
The Following 52 Users Say Thank You to AllGamer For This Useful Post: [ Click to Expand ]
 
AllGamer
Old
(Last edited by AllGamer; 6th September 2011 at 10:00 PM.)
#2  
AllGamer's Avatar
Retired Forum Moderator - OP
Thanks Meter 1571
Posts: 11,516
Join Date: May 2008
Location: buried under loads of work IRL

 
DONATE TO ME
NOTES:

It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.

If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else


To simplify things with the Command Line, it's best to copy and paste the contents inside ..\android-sdk-windows\platform-tools to ..\android-sdk-windows\tools
that way you'll have all the necessary files in the same location to prevent errors


MIRROR:
since CW website seems to be down, here's a mirror for the Image file.
download the 7zip attachment, unzip and flash recovery.img (recovery-clockwork-5.0.2.0-crespo.img)
Attached Files
File Type: 7z recovery-clockwork-5.0.2.0-crespo.img.7z - [Click for QR Code] (4.04 MB, 10355 views)

Donation is appreciated but not required, a cup of Coffee would suffice

Samsung i9000m: on CM10
Samsung Nexus S: on JB 4.2.2
Samsung Galaxy S II SGH-T989: on CM10
Samsung Galaxy NOTE SGH-i717r: on CM10
Samsung Galaxy NOTE 3 SM-N900W8: stock 4.3
The Following 4 Users Say Thank You to AllGamer For This Useful Post: [ Click to Expand ]
 
lordjone
Old
#3  
Senior Member
Thanks Meter 81
Posts: 107
Join Date: May 2010
Good guide but i have a question,
didn't you miss the step about renaming the install-recovery.sh script
that reflash recovery if crc is wrong?
 
Cubfan185
Old
#4  
Junior Member
Thanks Meter 1
Posts: 4
Join Date: Aug 2010
Thank you sir, I was hoping for a good step-by-step guide for us first-timers.
 
sinatosk
Old
#5  
sinatosk's Avatar
Senior Member
Thanks Meter 3
Posts: 154
Join Date: Oct 2009
Nice guide.

The only thing that's making me hesitate to do root on my NS is reversing the whole process...

stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...

I'll wait until google releases a firmware that contains everything
Google Asus Nexus 7 16GB
Google Nexus 4 16GB
 
AllGamer
Old
#6  
AllGamer's Avatar
Retired Forum Moderator - OP
Thanks Meter 1571
Posts: 11,516
Join Date: May 2008
Location: buried under loads of work IRL

 
DONATE TO ME
Quote:
Originally Posted by Cubfan185 View Post
Thank you sir, I was hoping for a good step-by-step guide for us first-timers.
thank you, that was the idea.

many of the GUIDEs we have here are usually aimed at people that already knows what to do, which usually leaves out all the 1st time owners of the phone.

Donation is appreciated but not required, a cup of Coffee would suffice

Samsung i9000m: on CM10
Samsung Nexus S: on JB 4.2.2
Samsung Galaxy S II SGH-T989: on CM10
Samsung Galaxy NOTE SGH-i717r: on CM10
Samsung Galaxy NOTE 3 SM-N900W8: stock 4.3
The Following User Says Thank You to AllGamer For This Useful Post: [ Click to Expand ]
 
AllGamer
Old
#7  
AllGamer's Avatar
Retired Forum Moderator - OP
Thanks Meter 1571
Posts: 11,516
Join Date: May 2008
Location: buried under loads of work IRL

 
DONATE TO ME
it's fairly simple, the instructions are as simple as this
http://forum.xda-developers.com/showthread.php?t=884097

and you can choose any stock ROM to flash back

Quote:
Originally Posted by sinatosk View Post
Nice guide.

The only thing that's making me hesitate to do root on my NS is reversing the whole process...

stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...

I'll wait until google releases a firmware that contains everything

Donation is appreciated but not required, a cup of Coffee would suffice

Samsung i9000m: on CM10
Samsung Nexus S: on JB 4.2.2
Samsung Galaxy S II SGH-T989: on CM10
Samsung Galaxy NOTE SGH-i717r: on CM10
Samsung Galaxy NOTE 3 SM-N900W8: stock 4.3
The Following User Says Thank You to AllGamer For This Useful Post: [ Click to Expand ]
 
Cubfan185
Old
(Last edited by Cubfan185; 2nd January 2011 at 09:35 PM.)
#8  
Junior Member
Thanks Meter 1
Posts: 4
Join Date: Aug 2010
Alright, just did it successfully. I had a few problems when installing the SDK and using fastboot. The recovery image must have been corrupt a few times for me. I had to take the battery out because it was stuck at the Google screen. My heart skipped a beat at that point, I didn't want to brick anything. Also had to put a required .dll file in the tools directory and the drivers were giving me problems, but got it all figured out. Thanks again.

Edit: Any reason why root required apps are saying they don't have root access?
 
KidYing
Old
#9  
Junior Member
Thanks Meter 1
Posts: 13
Join Date: Oct 2009
Will Google definatly release a full restore firmware of the current ROMS, something simular to an HTC RUU, or is it just something we're hoping they'll do?
 
onicrom
Old
#10  
Senior Member
Thanks Meter 47
Posts: 242
Join Date: Aug 2010
silly question... which fastboot binary did you use? the one from the htc developer site?

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes