Dude this super one click method is not working for me.. I'm using XXKPH for i9003... i'm getting failed for it.. please help
Well, as I said, I did it on an HTC desire S. Probably slightly different...
Sent from my HTC Desire S using XDA App
Well that is not a SOC root method. That is a different one called CF-Root. People say it works fine for 2.3.x above versions of Android!
http://xdaforums.com/showthread.php?t=788108
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
SuperOneClick v2.1.0.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
2.2.1
Getting manufacturer...
HTC
OK
Getting model...
T-Mobile myTouch 3G
OK
Getting version...
300801
OK
Checking if rooted...
False
OK
Installing BusyBox (temporary)... - Step #1
868 KB/s (1062992 bytes in 1.195s)
OK
Installing BusyBox (temporary)... - Step #2
OK
Rooting device... - Step #1
660 KB/s (585731 bytes in 0.866s)
OK
Rooting device... - Step #2
OK
Rooting device... - Step #3
OK
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK
Rooting device... - Step #5
OK
Rooting device... - Step #6
False
OK
Getting mount path...
/dev/block/mtdblock3
OK
Remounting /system with read-write access...
OK
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Pushing su-v2...
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Roo t\su-v2' to '/system/xbin/su': No space left on device
OK
Installing su... - Step #1
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Roo t\su-v2' to '/system/xbin/su': No space left on device
OK
Installing su... - Step #2
Unable to chmod /system/xbin/su: No such file or directory
OK
Installing su... - Step #3
Unable to chmod /system/xbin/su: No such file or directory
OK
Installing SuperUser... - Step #1
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Roo t\Superuser.apk' to '/system/app/Superuser.apk': No space left on device
OK
Checking for busybox
[1] Segmentation fault busybox true
OK
Remounting /system with read-only access...
OK
OK
Running a SU test...
Test failed!
FAILED
why i cant root my android? :/
So I sat down with SuperOneClick v2.1.1.0 this morning to see if I could get any further than previous times and I was partially successful.
Basically in times past when I ran SuperOneClick I noticed that it could not read/write to a specific file in a hidden directory.
The /data/local/tmp directory has global read/write/execute permission but is hidden from view and not easily browseable.
NOTE: I used a free image hosting service for the images. If there's a better solution to view them, please let me know...
And after the running the first steps 1-6 it would fail once I unplugged the USB and plugged it back in:
So I used AndroidCommander http://androidcommander.com/ to browse into the directory and changed the two files listed previously to read/write/execute (777).
For example, here's the changes to I made to the sh file:
BEFORE:
AFTER:
I then tried SuperOneClick again and was able to get further in the process but still no root. (For further clarification, I actually made ALL files in the directory 777 just to make sure I did not miss something).
SuperOneClick finshed and did not crash happily
I have also attached the crashlog file which I believe may be of help to someone who understands what SuperOneClick is actually doing.
Code:--------- beginning of /dev/log/main D/dalvikvm( 378): GC_EXPLICIT freed 105K, 52% free 2634K/5379K, external 2824K/2951K, paused 50ms D/KeyguardUpdateMonitor( 177): received broadcast android.intent.action.BATTERY_CHANGED D/KeyguardUpdateMonitor( 177): handleBatteryUpdate --------- beginning of /dev/log/system I/ActivityManager( 177): No longer want bn.ereader (pid 600): hidden #16 I/ActivityManager( 177): No longer want com.android.bluetooth (pid 378): hidden #17 W/ActivityManager( 177): Scheduling restart of crashed service com.android.bluetooth/.pbap.BluetoothPbapService in 5000ms W/ActivityManager( 177): Scheduling restart of crashed service com.android.bluetooth/.opp.BluetoothOppService in 14999ms I/ActivityManager( 177): Start proc com.android.bluetooth for service com.android.bluetooth/.pbap.BluetoothPbapService: pid=2528 uid=10038 gids={3003, 3002, 3001, 1015} D/dalvikvm( 627): GC_EXPLICIT freed 16K, 55% free 2626K/5767K, external 2824K/3527K, paused 93ms I/ActivityManager( 177): No longer want com.modaco.visionaryplus (pid 653): hidden #16 I/ActivityManager( 177): No longer want imoblife.memorybooster.full (pid 646): hidden #17 I/ActivityThread( 2528): Pub com.android.bluetooth.opp: com.android.bluetooth.opp.BluetoothOppProvider D/KeyguardUpdateMonitor( 177): received broadcast android.intent.action.BATTERY_CHANGED D/KeyguardUpdateMonitor( 177): handleBatteryUpdate
Does the VT1008 even have BlueTooth as seen in the crashdump? Maybe another auto-root solution would work with some modifications?
rageagainstthecage is a root exploit via a fork bomb.
It IS a potentially malicious payload, BUT it is being used with owner's consent to root the phone.
The DreamDroid malware use exactly same payload - they are trojans, but this is a helpful tool.
It IS a dangerous tool in the wrong hands, but this is a root exploit, so you should exercise common sense and a little understanding of what it does and how it works.
Couldn't have been easier. However when I launched TiB after seeing the successful ROOT message box from the unroot app, I am not rooted.
Update to my post: ran again and Busy Box states that I am rooted.
Thanks...
When i run this .. The GUI just hangs with a blank screen .. no errors.. if i go to task manager there are two adb.exe processes and if i force close one the GUI closes.
Any ideas?