[How-To] Unlock, Install SU, Custom Recovery

[jeffreynothing43]

Busy Box Installer

Well, everything seems to be working fine and rooted...the only thing that was different for me that I haven't seen in other root processes was that I had to install busy box through the market app to use certain apps that require root. Is this normal and will it have any negative affects on my device? Sorry if this is a newb question.

 

[baap786]

That's normal. Your device will be/is fine.

Sent from my Nexus S 4G using Tapatalk

 

[nmoreman]

I'm still stuck, KSmithInNY, I have followed your instructions to a tee from post 72. I had wondered
about the drivers, loaded PDANet, phone does not show up as drive (such as USB under C drive),
but is clickable to disconnect and can drag and drop files, shows as Android 1.0. No exclamation
marks in Device Manager, shows PDANet and updated drivers when trying to point at anything else.

I deleted SDK, reloaded as well as Java, have all add-ons. Copied recovery . . . crespo.img to files.

Opened cmd, fastboot devices, does not bring up phone or recognize.

Opened cmd, typed first line, it took, but when typing "fastboot oem unlock" it comes back "not
recognized as internal/external command, program, or file"

I know computers are finicky, but so close, something is so small its driving me crazy, have spent
hours on this, and now its a challenge. So I will keep monitoring for any brilliant ideas.

 

[KSmithInNY]

I'm still stuck, KSmithInNY, I have followed your instructions to a tee from post 72. I had wondered
about the drivers, loaded PDANet, phone does not show up as drive (such as USB under C drive),
but is clickable to disconnect and can drag and drop files, shows as Android 1.0. No exclamation
marks in Device Manager, shows PDANet and updated drivers when trying to point at anything else.

I deleted SDK, reloaded as well as Java, have all add-ons. Copied recovery . . . crespo.img to files.

Opened cmd, fastboot devices, does not bring up phone or recognize.

Opened cmd, typed first line, it took, but when typing "fastboot oem unlock" it comes back "not
recognized as internal/external command, program, or file"

I know computers are finicky, but so close, something is so small its driving me crazy, have spent
hours on this, and now its a challenge. So I will keep monitoring for any brilliant ideas.

Until your phone shows up in fastboot devices, it's just not going to work.

-After installing drivers, have you completely shut down and restarted your PC?
-with the phone on (not in fastboot) what happens when you connect it to your PC? Does a pop-up come up saying it's installing drivers?
-Are you able to drag down the notification bar and mount as USB?
-Are you using the cable that came with the phone? If not, try it.
-Are you using a primary usb port on the machine and not on a hub? Try using a different port

 

[RamboDroid]

KSmithinNY is Winning duh

Second sentence of the warning.

I feel sheepish....

BIG Shout out to KSmith He has been tearing up this thread and may others. He has been so so fast tor respond and so patient with many of us who get a little over our heads or get a little to gitty to read ALL the instructions.

If he has helped you be sure to thank him that way he knows how need and appreciated he is!!

 

[KSmithInNY]

Just having fun dude The title of your post is pretty funny. I LOL'd

 

[betachains]

unrooting

I need to unroot my phone to get an exchange (horrible battery life). Can someone please link me to the stock recovery image? I don't have install-recovery.sh on my phone.

Thanks.

 

[jp22382]

After doing this you'll want to boot into custom recovery from now on using the fastboot menu. If you attempt to boot from recovery using ROM Manager you'll get a black screen.

So if I install ROM Manager, can I use it to flash a new ROM (once CM7 is available) or do we have to take manual steps?

Is there a way we can setup our NS4G so we can use ROM Manager fully?

I'm new to all this, so sorry if this is a dumb question

 

[Trun]

I finally got it figured out. It was because I was using Windows 7 64. GBhil's post in the Nexus S rooting forum got it working.

 

[nmoreman]

Betachains,

I found a stock recovery file from Samsung which I used to reload stock Gingerbread, it is posted at the beginning in General section for those that need it. I used Odin (love it, I know how to do that), to reload.
I had gotten stuck at bootloader, it is unlocked, but could do nothing else. This reloaded stock GB and kept
it unlocked.
Hope this is what you need.

And KSmithInNy, this is what I had to do after I used Superboot. I had had so many problems with unlock, then must have used wrong phone download, or my computer went down with a virus just after that which could've screwed everything.

So I have had too much fun fixing ****, all is running except my printer network, ugh

 

[enik]

Probably a stupid question but most rooting methods for the nexus S 4G talk about android 2.3.3 I was wondering if this method would work on 2.3.4 as well. Haven't gotten a straight answer yet

 

[KSmithInNY]

Probably a stupid question but most rooting methods for the nexus S 4G talk about android 2.3.3 I was wondering if this method would work on 2.3.4 as well. Haven't gotten a straight answer yet

Yes

 

[gmap516]

Can I revert back to stock easily with this?

 

[luckylui]

Hey ksmith,

My girl uses your roms from the optimus and I was wondering if you were gonna cook for the ns4g also? You did one hell a job w the op

Evo 4G --> Nexus S 4G

 

[KSmithInNY]

Hey ksmith,

My girl uses your roms from the optimus and I was wondering if you were gonna cook for the ns4g also? You did one hell a job w the op

Evo 4G --> Nexus S 4G

Thanks and thanks to your girl for using my work. I don't believe I'll be releasing any roms. If someone had an open source project for the phone I'd contribute but I don't have the time to maintain it.

 

[enik]

What is platform-tools? Help please.

 

[KSmithInNY]

What is platform-tools? Help please.

A directory that gets created when you install the sdk.

 

[simon.ponder]

KSmith, lend a hand, if ya got any ideas

So fastboot works fine, I have unlocked the bootloader, but I get these errors. Tried with both image files in my platform tools and on the sd partition.


C:\Users\Simon>fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
error: cannot load 'recovery-clockwork-3.0.2.4-crespo.img'


C:\Users\Simon>fastboot flash recovery recovery-clockwork-herring.img
error: cannot load 'recovery-clockwork-herring.img'

 

[KSmithInNY]

So fastboot works fine, I have unlocked the bootloader, but I get these errors. Tried with both image files in my platform tools and on the sd partition.


C:\Users\Simon>fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
error: cannot load 'recovery-clockwork-3.0.2.4-crespo.img'


C:\Users\Simon>fastboot flash recovery recovery-clockwork-herring.img
error: cannot load 'recovery-clockwork-herring.img'

You said you have them in platform-tools but your not in platform-tools. Your in \users\simon. Put the recovery in platform tools then CD in cmd to platform-tools and try again. Of course, while in fastboot

 

[simon.ponder]

I guess I was thinking that since I had platform-tools in my path variable, etc. I know that only works for programs that you would like to launch from anywhere. I guess that is what Tussin CF does to ya after several doses. Bad Cold. Thanks KSmith, good to see you come over from Optimus S land.