[Samsung Captivate Glide] txterron:
I've made this thread for anyone new to Android that, like myself, took it upon themselves to root their device and then install custom mod

Samsung Odin Download Mode Drivers (MUST have this or Kies, your choice.)

Odin 1.85 (Current version as of this guide)

CWMR5x_i927_recovery.tar.md5 (This is ClockWorkMod and you must install it to facilitate flashing a custom rom later)

Order of operations. Boot into Odin on the device (Vol UP + PWR), start Odin on the PC. Click "PDA" button, throw in CWM .tar.MD5 file, do not alter any other settings and click Start. Phone will reboot. Next, flash it with a rooted ROM. Search Devel forums; something stock (AT&T for me) that is rooted. We're not going MOD at this point, just giving ourselves access to the phone that our carrier would otherwise reject.

I fought for a very long time (hours) with "Unknown Device" in Device Manager and neither the ADB (Android Debug Bridge) nor any Samsung driver would help at all. Installing the Samsung drivers (or Kies) was the fix; it installed the special driver that Odin (Download Mode on the phone) needed to converse via USB.

Second item I fought with was hung/frozen Odin NAND writes. I still don't have a good "fix" for this except that I moved the USB connection to the back of my computer rather than it being plugged into the front. Both are root hubs. If anyone wants to chime in, go ahead. Running Odin as Administrator did not make any noticeable changes on my end either.

Finally; I flashed with boot.tar (a CarrierIQ-free kernel in the dev forum) ClockwordMod and finally a rooted mod for use with AT&T in that order. I could have probably skipped the boot.tar flashing since I used CWM after the fact. I read through at least a dozen threads trying to come up with a solution as to why the rooted mod kept freezing during NAND write and I came to the realization that the Non-CWM kernel was simply rejecting the rooted mod.. this may or may not be true but it makes sense to me.

Below takes you to your own custom mod, stripped down for your pleasure.

i927_OsiMood_v2.01.30.zip (This is version specific, it will undoubtably update)

To boot into Recovery, hold volume down and hit power; CWM will start eventually

Even though I have a MicroSD reader, I never could get CWM Recovery to read the damn thing. Once you've downloaded the OsiMod zip, rename it to update.zip You should be booted into Recovery at this point so scroll on down to "Mounts and Storage" Use Volume Up/Down to scroll, Power to select. Scroll down to the bottom and select "Mount USB Storage" with your USB cable plugged in. Go to My Computer, go to your Android device. Make a directory called Update, whatever. Put update.zip in it. Now back on your android select Unmount and go back to the top menu. Select "Install ZIP from SD Card" and "Choose ZIP from SD Card" then scroll down to your Update directory you made, select update.zip and cross your fingers.

Now you're done, easy peasy. One more thing, you need to add AT&Ts WAP crap.

Settings, Wireless and Network, Mobile Networks, Access Point Names. As of today, you CANNOT delete an entry if you fat-finger it.. so don't. Use the following settings:

Name: AT&T
APN: wap.cingular
Proxy: leave blank
Port: leave blank
Username:WAP@CINGULARGPRS.COM
Password:CINGULAR1
Server: leave blank
MMSC: http://mmsc.cingular.com
MMS Proxy: wireless.cingular.com
MMS Port: 80
MCC:310
MNC:410 (note. this could also be 310, 41 or 15)
APN Type: leave blank

And for the gTalk addition, you need the following:

Google Android SDK

GoogleTalk APK Files (Only needed if you use gTalk, OsiMod strips it out and you cannot get it at this time from the market)

I will not go into great detail but you need to download the SDK and run SDK Manager. Install Platform Tools because you'll need Android Debug Bridge to throw commands at it. Read the thread above for instructions how. If you get "Operation Not Permitted" when trying to remount the system partition as RW, you'll have to open an ADB shell and:

mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system /system/app /system/sys

Leave ADB shell (control D or Exit)

Push the two files as instructed. They must be in the working directory you're in at that very moment to get copied from your PC to the android device

Now get back into shell

chmod 755 /system /system/app /system/sys

Again, feel free to chime in with errors I've made. The above is a method that personally worked for me, there are probably easier ways.