[Nexus S General] InitiatePenguin:
I'm putting this in General because this is my first time I've actually posted on XDA and I hope someone will move it to wherever it needs to be.

I've rooted my Nexus S a long time back when it was new, originally had some trouble with fastboot hanging on "waiting for device" I want to say trying PDANet fixed my problem then. I'm not foreign to the flashing/rooting process. And I know this is a long post but If you can please read it all it would be appreciated.

My Story:

>ICS was released and while Google said Nexus S would get an official update I saw some on XDA that were promising ports.

>I downloaded We Scream for Ice Cream Beta 9 and installed through Rom Manager

>About a month later I'm fed up with all the force closes and missing features the thread didn't inform me on and went to find another ICS Port.

>Downloaded and about to install through Rom Manager I'm informed that I need Clockwork (strange because I already have it) so within Rom Manager I flashed a new one.

>Install via SD Card and my phone reboots and then instead of loading recovery and doing its stuff I wait at the Bootloader screen. I try entering recovery myself and my phone restarts and again I'm at the bootloader screen.

>At the very bottom of the screen in gray lettering it says Fastboot FAILEDcommand

(As of now it displays the Google Logo with the unlock icon and hangs)

>At this point I decide I' going to flash over clockworkmod myself via adb. This should be the magic formula: via addictive tips (new user, can't include hyperlinks)

adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img

>Adb gives me an error similar to won't link after the mount/remount command. Also trying to cp the flash image to bin fails to work.

>I boot my phone, open Total Commander and try to copy the flash image myself to the bin folder in my root and it fails

(As of now I get error: device not found)

Then i think alright, maybe it's my drivers. I tried several different drivers from different tutorials because perhaps they are different in some slight way. >Whenever I try a new driver I can pick "adb Composite" "bootloader" or vanilla "adb interface".

>My device appears as "Android Phone" as the first entry in the Device Manager and the icon is a monitor with a small PCB chip in the corner.

>When the divers are completely uninstalled it appears in Other Devices with a yellow exclamation point.

>My understanding is that while it will automatiaclly grab the driver for USB mode, I have to force it to install the bootloader driver for when my phone is in the bootloader screen.

>And USB Debugging has been checked for everything I've done.

>Now i try to use PDANet, first I uninstall the drivers and install PDANet. Message appears saying there is already an Android Driver installed, I choose reinstall, select Samsung, pop says are you sure you want this driver, publisher cannot be confirmed? I click yes, I beleive that happens twice, it installs and then runs. It installed the vanilla "adb interface" driver.

(This is where I'm at now, the Fastboot FAILEDcommand is also gone.)

So now I'm like well there's fastboot, let me see if it recognizes it.

>Fastboot devices: nothing appears

>fastboot flash recovery recovery.img : it hangs on waiting for device.

>Same goes for other commands like OEM unlock.

All the while ROm Manager insists I have clockwork recovery verison 5.x - only it wont load and none of my PC options are recognizing the phone. So I can't flash over a different recovery image, and there;s nothing under alternate recovery in Rom Manager.

And the strangest of them all which may be Rom Manager's problem is that Super User FCs as soon as I try running it. Rom Manager states Super User gives it power at the end of the clockwork recovery flash, however, still says it's successful.

Before this entire thing my phone tried to OTA update to 2.6.7 for Google Wallet and where it would normally respond I got the Android Guy with a box and a yellow exclamation. This is also what I got when I first had some problems rooting months back before I flashed over images and roms. I figured it wouldn't update because it needed the stock recovery image and wasn't compatible updating with clockwork mod (however i think my phone has updated before with this method.)

I wouldn't mind rolling back to my stock deodexed version of Gingerbread at this point because the ROM I have now for ICS NFC and Bluetooth wont work among a slew of problems. And NFC was the major update in 2.6.7 in regards of tap to share and Wallet.

So I either need ADB and Fastboot to recognize my device to try reflashing clockwork and an Entirely new ROM remotely (if that's possible) or get clockwork mod on my phone to open.