[Captivate Q&A, Help & Troubleshooting] RichMD:
Log rooting KB2 with SuperOneClick 1.95

I got my new warranty replacement which I will load a custom ROM on soon. However, I rooted this one to verify SuperOneClick 1.95 works. Below is the log. First I ran made sure debugging was on. Then I disabled my AV (Windows 7 32bit) and ran SOC as an administrator. I then chose "root" and it ran through the first part showing "failed" at the end. I then tried "Shell root" and it said it was already rooted. SuperUser did NOT show in the app list. I ran "root" again and it flashed through screens (bat files) like it did before (more this time though) and it came up "Automatic OS check failed - is it 2.0 or higher?" to which I clicked "yes" and then it eventually listed another dialogue "BusyBox is not installed - do you want me to install it?" to which I said yes and then it worked the second time - at least the SuperUser app shows up. I then downloaded Titanium Backup and it failed to get root on startup. I then chose "Problems" in TB and chose "Upgrade SuperUser" which downloaded a newer version - I think it didn't show up when looking in the market directly. I tried updating SU via settings - check for a new version (which there was) but it kept failing. I could push packages via Droid Explorer though so I had "root". I tried rebooting into recovery but it was still 3e recovery. After rebooting the phone I was able to go into SU, settings, check for a new version and it successfully installed and was granted superuser permission. TB then worked, SGS Tools, etc. Sorry for the long post but hopefully it will be helpful.

This is the 3rd KB2 build that I rooted via 1.95 - it takes a little bit but it works. After looking at the log, this process would probably have been quicker if I rebooted the phone right after the second root attempt but I did what I did last time and it worked...

------------------------------------------------------------------

SuperOneClick v1.9.5.0

Checking drivers...

Killing ADB Server...

OK

Starting ADB Server...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

OK

Waiting for device...

OK

Getting OS Version...

2.2

OK

2.2

Pushing psneuter...

1606 KB/s (585731 bytes in 0.356s)

OK

chmod psneuter...

OK

Running psneuter...

OK

***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***

Killing ADB Server...

OK

Starting ADB Server...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

OK

Waiting for device...

OK

Running psneuter...

ROOTED

Pushing busybox...

2153 KB/s (1062992 bytes in 0.482s)

OK

chmod busybox...

OK

Getting mount path...

rootfs / rootfs ro,relatime 0 0 tmpfs /dev tmpfs rw,relatime,mode=755 0 0

FAILED

SuperOneClick v1.9.5.0

Killing ADB Server...

OK

Starting ADB Server...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

OK

Waiting for device...

OK

SuperOneClick v1.9.5.0

Checking drivers...

Killing ADB Server...

OK

Starting ADB Server...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

OK

Waiting for device...

OK

Getting OS Version...

OK

Pushing psneuter...

1851 KB/s (585731 bytes in 0.309s)

OK

chmod psneuter...

OK

Running psneuter...

ROOTED

Pushing busybox...

2189 KB/s (1062992 bytes in 0.474s)

OK

chmod busybox...

OK

Getting mount path...

/dev/block/stl9

OK

Remounting system with read-write access...

OK

Pushing su-v2...

246 KB/s (26264 bytes in 0.104s)

OK

chmod su...

OK

Pushing Superuser.apk...

1411 KB/s (196521 bytes in 0.136s)

OK

Creating /system/xbin...

mkdir failed for /system/xbin, File exists

OK

Checking for busybox

Copying busybox (/system/xbin/)...

OK

chmod busybox (/system/xbin/)...

OK

Installing busybox (/system/xbin/)...

OK

Remounting system with read-only access...

OK

Running a SU test...

Success!

Don't forget to reboot!