yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] TwoGunsGeronimo:
awesome....not booting into the recovery.img

i've wipe my data/factory reset and still can't get it to boot into recovery.

help please?
[Nexus S Android Development] NicholasQ:
Ok, I have a weird problem. Adb connects fine and everything. I can run adb commands, but as soon as I put phone into bootloader it pops up as a new USB device on my computer and prompts me to install the driver. I tried using the same usb driver but for whatever reason it just does not work. Why would my computer recognize it as a different device when it already has the driver installed and working fine when the phone is on?
[Nexus S Android Development] NicholasQ:
I've googled this issue quite a few times. what am I doing wrong? Why is the fastboot usb driver not included in the most recent SDK? ADB usb driver works fine.
[Nexus S Android Development] yungfresh:
Well I can't use root exploror because I don't have superuser permissions working so it won't allow me to r/w only r/o so my recovery went back to stock which means I can't mount the storage to set those commands. Please help.
[Nexus S Android Development] yungfresh:
Can I use the adb shell, cd/system/bin,chmod 6775 su commands while in fastboot?
[Nexus S Android Development] yungfresh:
Any idea how I would use the command on a mac? I did adb shell correct and got the "#" now how do I correctly use cd/system/bin? and chmod 6775?
[Nexus S Android Development] yungfresh:
I get permission denied after I input system/bin. any idea what i need to do? Thanks. I am soo close.
[Nexus S Android Development] nyijedi:
I got root using this method and it's working fine, however my recovery did revert back to stock. I see the posts on how to fix this, however, when I first flashed recovery using this method, it completely wiped all of the data on my phone. Is this normal? If I rename install-recovery.sh to install-recovery.sh.old, then flash the clockwork recovery again, will my phone be wiped yet again?
[Nexus S Android Development] mortzz:
I lost WiFi with rootboot.img It just errors out.

Anybody have the stock boot.img?
[Nexus S Android Development] DKYang:
Just type those 3 commands in order. Make sure you type it right, otherwise it will not work.
[Nexus S Android Development] daffyno:
i flash recovery "crespo" and at first it works but when i do a reboot the recovery does not work anymore

why?
[Nexus S Android Development] DroidRC1:
Me too :confused:
[Nexus S Android Development] daffyno:
after root u can use rom manager...full support for nexus s!

i solved so ;)
[Nexus S Android Development] DroidRC1:
Worked for the first time then it went back to stock recovery
[Nexus S Android Development] Mr.zeus:
doesn't it need HBOOT file or something like that?

i mean is that too easy to root Nexus s
[Nexus S Android Development] jblade1000:
rename the install script in the /etc folder, then flash CWM Recovery from Rom Manager. power phone off, fastboot, then go to recovery to make sure. then reboot.
[Nexus S Android Development] jblade1000:
for the record, the below commands

adb shell

cd /system/bin

chmod 6775 su

are something i've never ever done, and i have root just fine (three times now). Can someone explain why they think this is necessary? in CWM recovery, after mounting /system first, then installed the superuser zip from internal storage, all i do is reboot, check apps for superuser, and then download all of my root apps and they all work. all of em. just curious...

*edit* just thought about it, does that give super user permissions through adb specifically for "adb stuff" (vs. the superuser app giving permissions within the phone)?
[Nexus S Android Development] DroidRC1:
thanx..but the only problem is my root explorer apps (es file explorer & Android mate) won't mount to my system :confused: and I can't buy apps on the market so I can't get root file explorer app..so is there a way for me to rename that with in adb or something and if so can you show me what to type in my cmd...thanx

(o nevermind I can't get adb remount to work for some reason..it works for my nexus one but not nexus S :confused: )
[Nexus S Android Development] jblade1000:
sorry, im definitely the noob here when it comes to adb and the command line stuff, I used Root Explorer for my rename. Im sure others with far more knowledge than me can chime in though
[Nexus S Android Development] DroidRC1:
my root explorer apps (es file explorer & Android mate) won't mount to my system and I can't buy apps on the market so I can't get root file explorer app..so is there a way for me to rename that with in adb or something and if so can anyone show me what to type in my cmd...thanx
[Nexus S Android Development] sax1981:
Can someone please confirm the above. Will rooting prevent OTA updates for the Nexus S? Thanks.
[Nexus S Android Development] Dallas Johnson:
Thanks! Got root!

When I reboot I lose recovery though is this normal?

And how can I keep custom recovery screen?

Also my wi fi tethering is no longer working any one else

Have this problem?
[Nexus S Android Development] dm5363b:
Wifi error

Hi,

I wasn't paying attention while using this method to root my nexus and inadvertently flashed the wrong boot img. Thus once I booted up the wifi option on the phone no longer worked. I went back and flashed the correct file but that didnt fix the issue. Does anyone know where the wifi file is kept? Can I grab it from CM7 and replace the file? Any help would be greatly appreciated.

Thanks

Kris O
[Nexus S Android Development] poulosjr:
Being rooted definitely eliminates OTA updates because it replaces the boot.img
[Nexus S Android Development] bananenlarry:
if you root using koush's method without doing the optional part (boot.img) ota updates should be possible although you got root;)
[Nexus S Android Development] jblade1000:
This. All depends on the method you used to root. Although correct me if I'm wrong but don't you need stock recovery as well in order for the OTA to actually flash successfully? As we all know, receiving the update notification is one thing, successfully updating is something different ;)
[Nexus S Android Development] knytphal:
That's what I experienced. I hadn't flashed the optional image from the OP, when I received the OTA notification it was unable to flash successfully. I ended up just doing it manually.
[Nexus S Android Development] Dallas Johnson:
My camera isn't working now either :(
[Nexus S Android Development] kindiboy:
if you are having problems follow the instructions on the link below

http://xdaforums.com/showthread.php?t=882333

AND THIS GUIDE NEEDS TO BE EITHER UP TO DATE OR DELETED!
[Nexus S Android Development] jblade1000:
Well theohetically, since 2.3.1 introduced a script that reinstalls stock recovery at reboot, anyone (including myself), that simply renamed the script so it didnt execute, should be able to rename it back, reboot, let it install, get stock recovery, and then update without issue. Key word being should...:rolleyes:

I read through that thread and I'm wondering how its different if its still flashing a boot image?(pardon the noobness)
[Nexus S Android Development] kindiboy:
It's different because it takes into consideration which version you have 2.3 or 2.3.1, to each a specific .img is required.
[Nexus S Android Development] Dallas Johnson:
Thanks I just re did the superboot with the newer version and now my camera and everything is working :) now time to theme
[Nexus S Android Development] ptm:
Sorry for the total n00b question, but where do i put your recovery img file to flash that? Also, am I right in thinking i need to chang the file name in the OP to reflect the '3.0.0.0' part?

ta in advance for your help chaps!
[Nexus S Android Development] mcosmi:
thanks.

thanks for this....it's exactly what i needed to enable SU. I am now cruizing with root.
[Nexus S Android Development] heinrich:
Wifi error, camera broken on 2.3.1

I had a hard time getting root but finally got it with the chmod method. Rom manager still errors when I choose "fix permissions".

Wifi will not start, just says error.

Camera crashed with an option to force close or report.

I reflashed the stock boot image posted elsewhere and it fixed the camera but not wifi.

I really need wifi, can someone please help?

Edit 1: I tried rom manager's stock nexus s rom, didn't fix wifi, camera still works
[Nexus S Android Development] heinrich:
Momohammed20 resolved my wifi issue with his full restore stock image and excellent write-up here: http://xdaforums.com/showthread.php?t=884093

YAY!!!
[Nexus S Android Development] heinrich:
Koush:

Something I don't see addressed anywhere:

Your instructions say to download recovery-clockwork-3.0.0.0-crespo.img

But then you say to flash recovery-clockwork-crespo.img

Are we assuming you mean to rename the 3.0 file to the name you use in your flash instruction, or alternatively to:

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

I renamed the 3.0 file and flashed but ended up with a really messed-up device that had no wifi, camera etc. Only after restoring Momohammed20's stock system rom did I get full use back of my phone. Not saying at all that this is your fault, but it just seems weird that your instructions are so clear, and others seem to have succeeded following them, and yet you say to flash a file different from the one you just said to download?

Best wishes for the new year,

Heinrich
[Nexus S Android Development] stonew5082:
You have to point to the correct file name. Koush did a really bad job with the directions! Make sure you are putting the ENTIRE file name into adb! the 3.0.0.0 part AND the file type, .img! And make sure you point the correct folder! Make sure the recovery file, AND the adb file are in platform-tools (move them there, it makes everything easier) and make sure you are pointing adb to the correct place: android-sdk-windows\platform-tools\ NOT just android\tools. ADB is not magic, its pointing to a specific file and place.
[Nexus S Android Development] nicholasbgr:
Is there any downside of doing this?
[Nexus S Android Development] AllGamer:
that's an excellent question.
[Nexus S Android Development] knytphal:
Well, I suppose that if your custom recovery should ever get fouled up in some freak accident you might wish you hadn't renamed the install-recovery.sh file. ;)

I've left mine alone, I figure it isn't too difficult to flash CWR whenever I need to make changes. Not that I reboot the phone a lot anyhow.
[Nexus S Android Development] allyn274:
I followed all the instructions from the video on the unlockr dot com about how to root the samsung nexus S (THANKS!) - and ended up with the bootloader unlocked. But when I tried to go to the next step with the recovery, i just got the white/yellow triangle with the android icon and couldn't go further. Had to reinstall all my applications and everything - would rather not do that again. Can anyone please advise where/how to pick up?

- Superuser.zip file is in my internal storage, but was unable to get to recovery to flash it. That's where the triangle came up.

Thanks all. This site is super helpful.
[Nexus S Android Development] nicholasbgr:
Did you manage to flash clockworkmod? Are you booting into the OS after flashing the recovery? If the answer is yes, the clockworkmod you just flashed is being overwriten by the stock one, it's a security measure in gingerbread and it has been discussed a couple pages ago.
[Nexus S Android Development] Luxferro:
That's like saying you don't want to use a custom rom, cause it might mess up, so you'll stay on stock. Or you don't want to root, or unlock the bootloader, cause it might mess up... you get the point. But to each his own.

You always have Fastboot to restore any recovery you want.
[Nexus S Android Development] yungfresh:
So clokwordmod came out with an update I noticed when I downloaded the update for Rom manager, but now for some reason I can't boot into the cwm 3.0.0.5. Anybody found a way around this? I'm stock on stock recovery.
[Nexus S Android Development] yungfresh:
update: It works now.
[Nexus S Android Development] armisis:
Fastboot OEM unlock??

I went into the fastboot mode as instructed however I cannot find a OEM unlock function. So I'm stuck there.... (I'm so happy to see your work with the Nexus S and look forward to a stable Cyanogenmod for it! I am in an area where I need the full market but am unable to get it...)

Thanks,

Armisis
[Nexus S Android Development] distortedloop:
There's no OEM unlock function in Fastboot menu on the phone.

I was going to say you should double check the instructions, but they're actully not that clear.

You boot the phone to fastboot, then FROM YOUR PC/MAC, use the terminal to type "fastboot oem unlock" and I believe it should then pop up a warning on the phone asking if you're sure. Say yes. IIRC it reboots.

You're going to need the sdk toolkit drivers and the adb and fastboot binaries installed on your computer. You should probably be in the directory that the fastboot is in, or have it in your path.
[Nexus S Android Development] ogdobber:
try going here http://xdaforums.com/showthread.php?t=875630

and here http://xdaforums.com/showthread.php?t=878786
[Nexus S Android Development] psyclobe:
This didn't work for me, the su program never got installed properly. To fix I went in and manually deleted the /system/sbin/su /bin/su /system/xbin/su and then just pushed su to /system/bin and then symlinked to it from /bin.
[Nexus S Android Development] giodesi1965:
But having unlock, root and Recovery clockwork I lose the ability to have and install OTA official updates ?
[Nexus S Android Development] mikelaggelos:
i believe this guide is only for advanced users. i had to read three different guides to root my nexus s. anyway thanks Koush for all the goodies
[Nexus S Android Development] lmerega:
Guys, do you think we could find a blocked "fastboot oem relock" after a FW upgrade?

I mean: they could decide to make impossibile for us to relock the phone if tey wanted... right?

TIA
[Nexus S Android Development] ogdobber:
first of all...No. this is a pure (devleoper) google phone. not some evil carrier driven phone or even a samsung controlled phone. so you will never see that happen

secondly...who cares
[Nexus S Android Development] michaelmruffin:
I followed the instructions but the recovery does not hold. When I reboot my SNS, it returns to the stock mode. Help!!!
[Nexus S Android Development] michaelmruffin:
Will Not Hold Root

I'm stumped. I rooted my Nexus S with Clockwork Mod 3.0. I can get to recovery to flash the SU but when I reboot, it returns to stock as if it was never flashed at all. Suggestions....
[Nexus S Android Development] allyn274:
Odd behavior with notification tones....

Ever since I unlocked the bootloader and rooted my phone, every time I power the phone off (frequently while travelling recently), all of my ringtones change. And I've lost the ability to select a different tone for the calendar reminders. I can select it, but it always goes back to default. And any custom notification tones I've set for other programs (messaging, etc.) - it just picks its own when rebooted.

Any thoughts? Please?
[Nexus S Android Development] michaelmruffin:
Will not go to Recovery After Reboot

I followed the instrucitons to a "T". When I flash the img, I can go to recovery. When I reboot to flash the root and go to recovery, I get the dreaded exclamation point. What am I doing wrong here?
[Nexus S Android Development] irishrally:
Yes, but this is a good trade off in most people's opinions as this forum will usually have the update as quickly as the OTA.

If you have the stock ROM when you reboot the custom recovery you just flashed will get over written by the stock recovery. Put the custom ROM you want to load on the root of the internal sd card and flash it in clockworkmod recovery.

It's a known bug in Gingerbread that custom ringtones don't always stick after a rebooot. Should be fixed soon, if not already in the 2.3.2 update.
[Nexus S Android Development] Highland3r:
Another option is to delete (or better just rename) the following file:

/etc/install-recovery.sh

Should stop the default recovery being applied on boot.
[Nexus S Android Development] IDtheTarget:
I've been trying to root my phone, not much luck. I manually installed the 2.3.2 update yesterday.

I've been following the directions here: http://xdaforums.com/showthread.php?t=895545

but when I try to flash superuser, it gives me an error about the signature.

I see in koush's downloads directory that there's a 3.0.0.5 img: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img

Is this one better, and will it let me flash super user?

Thanks!
[Nexus S Android Development] ogdobber:
try this superuser
[Nexus S Android Development] IDtheTarget:
Okay, sorry, I'm a freaking idiot. I wasn't getting into Clockwork recovery after all.

I installed ROM Manager and flashed the recovery, and was able to get into the Clockwork recovery and flash the super user.

I think I need to go get some sleep.

Thanks, all!
[Nexus S Android Development] murdoch1:
Crespo or Herring

Hi Guys.....just upgraded from HTC Desire to Nexus S......absolutely love the Nexus.....no more Sense.......LOL.

Anyway I am attempting to install Cianogen 7 MOD however experiencing issues. The rom installs but Superuser is messed up. Just noticed on my bootloader my product name is "Herring".....does this mean I have to flash a different Recovery Rom? :):)
[Nexus S Android Development] distortedloop:
This doesn't seem like the proper place to be asking about this (maybe try the cyanogen mod thread), but anyways, did you try reinstalling superuser and/or the su binaries? Seems like Cyanogen mod would include proper root files in the build already, but try booting to clockwork recovery and re-running the su update zip file from cw.
[Nexus S Android Development] AndyCr15:
Is there a working download for the 3.0.0.5?
[Nexus S Android Development] distortedloop:
Here's the mirror off koush's blog site: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.5-crespo.img

Just worked for me.

And here's the main blog link in case an update comes out for newest versions: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
[Nexus S Android Development] AndyCr15:
Nice one mate, thanks.
[Nexus S Android Development] tru2malice:
I understand cyanogen not supporting g1 in gingerbread form but as far as koush is concerned he should have let us g1 users know. I didn't purchase Rom manager until a month ago then i find out a week or so later that there is not gonna be any support for g1's and of course he wont respond and he wont refund me .All the nightly's dissapeared even from koushes server so g1 users be warned don't purchase rom manager this im going to post on every android forum on the net. Due to koush isnt letting g1 users know whats happening and as far as im concerned if there is no support then there shouldnt be a rom manager at all. So as to be totally honest with all the devices rom manger has bricked and the lack of support i am going to even go so far as to say even if you dont have g1. Be forwarned any issues dev wont respond emailed him from multiple email addresses and emailed more than one of his emails. So stay away from all clockwork mods and rom manager.To top it all off wes gardner is maintaining cyanogen gingerbread but within the nightly builds by koush it specifically says avoid wes gardner at all costs so just shows what koush is about. So it goes without saying avoid koush at all costs wish he wasnt part of they cyanogen community everything about cyanogen is open source except anything koush makes lol what does that say that he isnt about what cyanogen stands for he is giving cyanogen a bad name and rep.

By the way im not saying koush is not a amazing proggrammer

cause he is but personality portrays everything in life......
[Nexus S Android Development] kurrupt_1:
Is there a tutorial on how to do this on a Mac? I need mad help.
[Nexus S Android Development] distortedloop:
Yes, there is, just a few threads below this one in this section. Check this one out: http://xdaforums.com/showthread.php?t=931865

Normally I'd recommend my own guide, but it assumes you know a few things already that the above one doesn't.

I don't like the order the Mac guide author has you do the steps, and he has you do the oem unlock which is not necessary (see my guide to why) and wipes all data off your phone (including sdcard contents).

With that in mind, following his guide, consider modifying it slightly per these suggestions:

You should skip step #5 (the fastboot oem unlock command step) even if your bootloader is locked) unless you want to wipe your phone and lose all data.

Also, I would copy the su update zip to your sdcard before starting the process rather than after, allowing you to skip steps 9-11 in that guide.

Ignore the stuff about relocking the bootloader, since you didn't unlock it.
[Nexus S Android Development] Kel Ghu:
"Wipe Battery Stats" option doesn't seem to work on my phone... I had to use the terminal or root explorer to delete the file.
[Nexus S Android Development] cis.snakeman:
Thank for this topic !

But I'm interested to install a rooted boot image.

In order to have adb has root by default, but the link to the image described above is dead (http://koush.tandtgaming.com//samsun...g/rootboot.img)

Some one can help me in that way, please ?
[Nexus S Android Development] knytphal:
Okay, I've got what I consider a stupid question....

I have a nandroid backup from this morning made with 3.0.0.5.

I'm now trying to restore that nandroid backup after deciding that I didn't like the rom I was trying out.

I'm unable to restore my backup. I've tried multiple times, both booting directly into recovery and selecting to restore that backup; doing the same only mounting /system and /data before trying; and doing the restore from Rom Manager itself. Each time it boots into recovery and looks like it's restoring everything like it should...but when I reboot after it's done it's not restored my data. The system looks like it's there as it's still rooted....but my data's not there.

I'm at the end of my rope here. I don't recall having this issue before.
[Nexus S Android Development] ogdobber:
try an older nandroid...that one appears to be corrupt
[Nexus S Android Development] knytphal:
Well that hasn't seemed to work either, I just tried a backup from about a week ago and am getting the same results....data is not being restored.

I'm trying an even older nandroid now.....I'm starting to run out of what's on my phone.

I'm starting to get depressed here... :(

EDIT:

Well, that is exceptionally depressing. I had to go back to a nandroid backup from mid-January to find one that wasn't currupt. That sucks. Fortunately I do a Titanium Backup twice weekly so I shouldn't lose too much. Damn, that sucks.
[Nexus S Android Development] distortedloop:
That's disturbing to read. Nandroid in Clockwork is supposed to make an md5 of the image to ensure it's not corrupted.

I've seen in the past where if your sdcard doesn't have enough free space to hold the entire nandroid set of img files that the nandroid gets corrupted; but I'd have expected the md5 part of the process to ensure against, or at least warn you against it.

If you had numerous iterations of nandroid backups on the phone along with other data, is it possible you don't have a lot of free space on the sdcard?
[Nexus S Android Development] croques:
Recovery Image Link Wanted

The link for the recovery image - http://koush.tandtgaming.com/recoveries/recovery-clockwork-herring.img appears not to be working.

Has anyone a working link; or could they post the image file here please?
[Nexus S Android Development] ionutz6:
+1 on this one. Just got my SNS, managed to unlock it, now trying to install CWM recovery. thanks.

EDIT: Just found it via google and uploaded here to this post.
[Nexus S Android Development] ogdobber:
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
[Nexus S Android Development] AllGamer:
that version is deprecated

a newer version 3.0.0.5 (latest) is mirrored locally here on message # 2

http://xdaforums.com/showthread.php?t=895545