[Android Software/Hacking General [Developers Only]] SharpIS03:
Trying SuperOneClick

Decided to give this program a chance too since I tried the other ones, and I was finally able to get the ADB driver to work.

First Method

1. Restarted the phone

2. USB Debugging is CHECKED

3. Plugged phone into the netbook

4. Started SuperOneClick, clicked Root

5. SuperOneClick will start looping after running RATC and trying to restart the ADB server. Left it like this for 5 minutes.

6a. IF I uncheck USB debugging while it says "Waiting for device" with the USB connection sound indicating a detected device, USB disconnection sound will play and program will wait. If I check USB DEBUGGING again then the program will resume looping

6b. IF I uncheck USB debugging at any time during the loop when the USB disconnection sound has already played (so before the starting up sound can play), the program will be unable to resume looping and just freeze despite shutting off any processes related to this procedure. At this point I need to restart both my netbook and my phone

7. Letting SOC loop for about 10 minutes will result in the program saying NOT RESPONDING and would then need a fresh restart

Killing ADB Server...

OK

Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

OK

Waiting for device...

OK

Pushing rageagainstthecage...
21 KB/s (5392 bytes in 0.249s)

OK

chmod rageagainstthecage...

OK

Running rageagainstthecage...
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 rageagainstthecage...
OK

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

Second Method

1. Leave USB DEBUGGING unchecked

2. Plug phone in, start SOC, click Root

3. When SOC says "Waiting for device", check USB DEBUGGING

4. RATC should start

5. When SOC says "Starting ADB server", uncheck USB DEB, check USB DEB, uncheck USB DEB again before the "Waiting for device" message appears again

I usually can't get this timing right due to some lag on my phone. I got it right a couple of times and after about a minute, SOC will have the NOT RESPONDING indicator on again. At this point, I can check USB DEB and the program might start on a loop again, or I need to restart...again.

With either of the two methods, if I go into my Task Manager on my netbook and kill one of the two ADB.exe (usually the one with the lower memory value) processes, then the program will say FAILED, like so:

***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 rageagainstthecage...

FAILED

Third Method

1. Power off phone, restart netbook

2. Start SOC, click Root

3. When "Waiting for device" message appears, connect phone to netbook

4a. If USB DEB was checked before turning off the phone, SOC will do the looping thing again when the phone is finished turning on

4b. If USB DEB was unchecked before turning off the phone, nothing happens when the phone comes back online

== tl;dr ==

It looks like it's getting stuck at the RATC process and loops from there until it freezes. Range of problems may include: bad USB cables, bad USB ports, and/or this IS03 is one tough SOB.