[APP]SuperOneClick v2.3.3 - Motorola Exploit Added!

Status
Not open for further replies.
Search This thread

amoamare

Senior Member
Jul 17, 2006
476
319
Sorry only read the last post about 2.3.X and not able to re-run the software again.
I'm certain its due to it not cleaning up the boom.sh files etc. if the files exists the exploit doesn't work.
 

FreddyFresh

Member
Apr 9, 2011
24
2
Östersund
Stuck at #6 using GingerBreak exploit with none Odin custom method.

fleV6.png




Samsung Galaxy S i9000 -XXJVO
 

hell_storm2004

Senior Member
Dec 15, 2010
252
8
Dallas, Texas
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 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 ----------

Well, as I said, I did it on an HTC desire S. Probably slightly different...

Sent from my HTC Desire S using XDA App

Hmmm.... I cant change modes with the cable connected on a Galaxy S. I tried to disconnect and reconnect as quickly as possible, but if i do that Step 6 fails, thus failing the whole process!
 

DetCochese

Senior Member
Aug 16, 2010
84
7
Unmarked Rustbox
I tried toggling USB Debugging when it hangs on step 6:

superoneclick2.jpg


---------- Post added at 02:57 PM ---------- Previous post was at 02:54 PM ----------

Toggling USB debugging BACK ON causes a R/W fail..

superoneclick3.jpg
 

josecleocir

Member
Sep 30, 2011
27
13
Joinville - SC
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? :/
 

mohsin002

New member
Oct 1, 2011
1
0
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? :/


You don't have any more disk space left. Try uninstalling some apps and then try rooting.
 

csbernar

New member
Sep 15, 2011
2
0
Problem with SuperOneClick

Hello, i am triyng to download SuperOneClick but the AV McAfee blocks it and say that is a trojan. What can I do to avoid this kind blocking? How can I say to McAfee to ignore?

Thanks.

Regards.
 

DetCochese

Senior Member
Aug 16, 2010
84
7
Unmarked Rustbox
Anyone???????????????

This is from a VTab thread. Halp!

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?
 

vladdangel

Account currently disabled
Jun 5, 2011
55
5
GB
meettomy.site
How long...

How long is it supposed to take when "Waiting for device"?
The super one click seems to freeze (hourglass, complete white box when switching to another window and back)

Stays there forever.

I just got a samsung captivate and it's not working. I saw a samsung tab, clicked the code thing and nothing happened at all there.

Edit: I reset the USB Debug off/on again and it went through. Just, no root. All root applications force close when asked for root function and the SU test didn't do anything.

Edit2: Rebooted phone, it works now. THANK YOU!!!
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 720
    SuperOneClick


    FOR ANDROID GINGERBREAD AND EARLIER DEVICES




    rootedgingerbreak.png

    Downloads available at http://shortfuse.org/

    v2.3.3
    ------
    Motorola ADB Patching
    Checks for shell root before applying exploits
    Unroot has been fixed to work more reliably
    LG devices no longer need to use alternate ADB

    v2.3.2
    ------
    Better LG phone support

    v2.3.1
    ------
    Auto driver installation

    v2.2 is up!
    zergRush and Superuser 3.0.6 included
    ----------------------------------------------

    v2.1.1 is up!

    Driver pack comes later!

    ---


    I made it. I tested it. It works. You can get it from shortfuse.org or use the links below (if you're a registered XDA member).

    Here's a one-click root with almost all phones and all android versions. (including the i9000, Droid, Nexus One, etc)

    YOU CAN ROOT ALMOST ALL ANDROID PHONES! :)

    The program requires Microsoft .NET Framework 2.0+ or Mono v1.2.6+
    Operations systems with native support:
    • Windows Vista
    • Windows 7
    • Ubuntu Hardy (8.04 LTS)
    • Ubuntu Jaunty (9.04)
    • Ubuntu Karmic (9.10)
    • Ubuntu Lucid (10.04 LTS)
    • Ubuntu Maverick (10.10)
    • Debian Lenny (5.0)
    • Debian Squeeze (testing)
    • Debian Sid (unstable)
    • Debian Experimental

    If you run Microsoft Windows XP, install .NET Framework v2.0 or above
    If you run Mac or another Linux flavor, make sure you install Mono:
    http://www.go-mono.com/mono-downloads/download.html

    For more information about making it work in linux:
    See here


    You NEED to put your phone on USB Debugging mode
    You NEED to install make sure the Android drivers for your phone are installed
    Make sure you DO NOT mount your SD card.
    If you still can't get something to run, try doing it in recovery mode.


    Read me: (READ BEFORE POSTING)
    2/24/2011:
    I registered my website shortfuse.org so you can grab SuperOneClick from there now.

    2/22/2011:

    Great news. -1Day roots AT&T Motorola Atrix4G!!! YAY!

    11/29/2010:

    I'm sorry I haven't been updating lately!!! The problem is, I no longer have an Android phone and I can't play around or test anymore. I'm going to see if I can find one on craiglist or ebay.

    11/10/2010:
    I finally figured out how to root without looping. After rooting 13 phones, this is how I did it on the first try.

    Turn USB Debugging OFF

    Click Root

    When it says: Waiting for Device, Turn USB Debugging ON

    It'll now run RATC

    When it says: Starting ADB Server...
    Turn USB Debugging OFF
    Turn USB Debugging ON
    Turn USB Debugging OFF
    All BEFORE it says "Waiting for device..." again


    11/1/2010:
    Hey guys! I'm sorry I haven't been able to respond to lots of posts. I've been really busy lately with work. I've been reading some posts and I've made some changes in v1.5.2

    Let me know what bugs and issues you guys have.


    10/17/2010:
    Thanks to all that donated! I was worried for a bit but you guys proved me wrong. So, I fixed the NMA (non market apps) button. It should now install sqlite3 and busybox into a temporary folder if you don't have it. I added an unroot (by popular demand). I did some major code clean up, so you can expect faster releases from here on out. Next version will add sqlite3 and busybox to the /system partition included in root.

    If you're having issues with "wait for device" or if RATC is looping, try this
    Unplug your USB Cable
    Go to Settings > Applications > Development
    Uncheck USB Debugging
    Plug in your USB Cable
    Unplug your USB Cable
    Check USB Debugging
    Plug in your USB Cable

    10/13/2010:
    I need people with issues to post their device model and if they tried rooting in recovery mode. All posts ignoring the read me will be ignored. (meaning nma complaints and those NAND locked devices).
    I'm getting flooded with replies, PMs and emails. Seriously, try reading a few posts back.
    The program has been downloaded over 5000 times and only 2 people have have donated. I see donations as signs of gratitude. Even if it's 25 cents, please donate.
    When I find the time (and will) I will work on the v1.5 release.
    The rageagainstthecage looping is by design. Bad usb cables and ports can cause ratc to not run properly so I have it loop until it works. The "waiting for device" hang is for the same reason. There's nothing wrong with my application. It's usually your usb cable or port. This is not a cop-out answer. This is not an excuse as if I didn't know why it happens. This has been investigated and the problem is USB connectivity. It happens with my Captivate as well.

    10/11/2010:
    Enabling market apps isn't working unless you have busybox installed. I plan to fix this in the next version. The problem is, different devices have different locations for the com.provider.android.settings/settings.db and I was using the 'find' command to find your settings.db location. I didn't realize this was a busybox command not internal. That will be fixed.

    I also added some information about root that I think people should read and classified different root levels.

    By classifying root levels, I make it easier for the users to know if certain options will work or not. For example, enabling non-market apps will only require a Level 1 root, meaning it will work with the HTC Aria

    Donate

    Donate if you wish... :)

    Compatibility list
    Please note that if you device is not listed here, it doesn't automatically make it incompatible. The list is definitely incomplete.
    Use the search feature to search for your phone model: http://xdaforums.com/search.php?searchthreadid=803682

    Incompatibility list

    With the absolutely beautiful ADB exploit I use, titled rageagainstthecage (ratc), absolute ALL devices can be rooted. This is because it exploit is ADB which all devices use. There is an issue though. Some devices have a NAND lock which does not allow you to write to the /system mount. Because of this, you can't copy su, sqlite or busybox to /system/bin. This creates some issues but there is a work around. For things that don't need access to /system (like enabling non-market apps) I can use the ratc exploit to make those changes. If your device cannot use su in /system/bin then you can simple select a checkbox (as of v1.5) that says to use ratc.

    There are 3 levels of "root" we can define:
    Level 1: Shell Root (with ratc rooting the adb shell but no /system write access)
    Level 2: Temporary Root (/system/bin/su installed but lost on reboot)
    Level 3: Full Root (/system/bin/su installed and sticks)

    Some devices have a NAND lock. SuperOneClick will only give a Shell root until you remove this lock.
    The following phones can use http://unrevoked.com to remove this lock:
    • Sprint EVO 4G (HTC Supersonic)
    • Droid Incredible (HTC Incredible)
    • HTC Desire GSM
    • HTC Desire CDMA (HTC BravoC)
    • HTC Aria
    • Droid Eris (HTC DesireC)
    • HTC Wildfire (HTC Buzz)

    THe HTC Legend and My Touch 3G 32A also have a NAND lock and need more specific methods to unlock.

    The T-Mobile (HTC) G2 has something different which may or may not be a hardware flaw. I have yet to really research the device, but while it may root, it won't be permanent since copying /su to /system/bin/su has problems. I believe this is a Level 2 root, but to be honest, I need to research more.

    All other devices has a Level 3 root via SuperOneClick

    Version changes:
    v1.9.5
    Driver Installation Fix
    Force Administrator on Vista/Win7
    Fixed Non-Market Apps not working for some devices

    v1.9.1
    GingerBreak support! (I think)

    v1.9
    Bug fixes!
    Should work better now on XP systems and Linux

    v1.8
    Automatic driver installation
    Removed RageAgainstTheCage (no virus flags)
    New folder structure
    Major code clean up

    v1.7
    Hopefully fixed Linux hangs
    Theoretical honeycomb support (still needs testing)

    v1.6.5
    Fixed major bug. Oops!

    v1.6.4
    Installs busybox to /system/xbin and installs syslinks
    Added a 30 second timeout check (should eliminate all lock ups)

    v1.6.3
    Mounts with busybox first
    Includes version in first line

    v1.6.2
    Fixed wrong su version being sent
    Fixed issue when getting OS version
    Prints device info on failure.

    v1.6.1
    Falls back to previous mount path method if busybox method fails

    v1.6
    Uses psneuter for exploit instead of rageagainstthecage by default (should root Sony Ericsson devices easily now)
    Added detection for 1.x Donut/Eclair kernels
    Uses busybox for getting mount path
    Updated Windows ADB to latest version (I'll update the Mac/Linux ones next build)

    v1.5.5
    Unroot uninstalls Superuser from /data/app
    Returned installation of Superuser to /system/app

    v1.5.4
    Fixed superuser install issue
    Added a prompt to tell you to allow superuser on your phone, for the test.
    Fixed unroot.

    v1.5.3
    Fixed ADB-pushing problem

    v1.5.2
    Administrative rights in Windows Vista/7 are automatically requested.
    Fixed the settings.db search. (Tries default two locations, then uses busybox is all else fails).
    Set Superuser to install (to data/apps) instead of copy to /system/apps. You can manually remove it from your phone like any other app. (You can also update it with the Market).
    Fixed NMA not working if you didn't have Shell Root


    v1.5.1
    Untested Mac and Linux support (you need Mono)

    v1.5
    Fixed Non Market Apps
    Added Unroot
    Added separate Shell Root (rageagainstthecage) button
    Lots of internal code clean up.

    v1.4
    Changed main form's name to SuperOneClick from RageAgainstTheCageGUI
    Enabled Captivate - Get Unlock Code button
    Added a messagebox to confirm if Non Market Applications are enabled
    Made "Enable Non Market Apps" FULLY universal
    Added initial message telling you to remember to allow superuser commands (when enabling Non-Market Apps)

    v1.3
    Removed busybox for space reasons. Changed the layout. Fixed issue where application stayed running in the background. Added Non Market App button.

    v1.2
    Added a detection to see if RATC was already working.

    v1.1
    Universal device support. Application now finds your /system path.

    v1.0
    Initial release.

    Development Plan:




    Scheduled for next major release
    • Linux support via mono-project
    • Add a check box to use su or rageagainstthecage for other scripts (like Enable NMA)
    • Better error handling for devices with NAND lock on /system
    • Have options show what level root is needed (0,1,2,3)

    To do list:
    • Jupiter fixes
    • Custom scripts support
    • Plugin support
    • Mac support via mono-project
    • Linux support via mono-project





    Wishlist:
    • None
    Thanks to basily, I have an Captivate v2.1 nv_data.bin I can test with to create the unlock button.
    I need a mac/linux user to help me. PM so we can chat on AIM/Google

    Courtesy of TheUnlockr.com, here's a step-by-step video:

    Mod Edit: this app will set off some anti virus software...here's a small explanation by pulser_g2:

    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.
    20
    For you linux users:
    To get ADB working:
    Install these libraries:
    apt-get install lib32ncurses5
    apt-get install lib32stdc++

    If you run ubuntu, see this:
    http://developer.android.com/guide/developing/device.html#setting-up

    Install Mono
    apt-get install mono

    Install WinForms 2.0 for Mono
    apt-get install libmono-winforms2.0-cil

    Mark adblinux as executable
    chmod 755 adblinux

    Open application with mono:
    For v1.5.1, it has to be launched from the same working directory as adblinux, so open terminal, browse to the folder and type
    sudo mono SuperOneClick.exe


    In the next release, I'll make sure I fix the "working directory" problem so you can just right on SuperOneClick.exe, hit "Open with other application" and select mono

    Screenshot.png
    9
    First reply!

    Thanks!!! Even I won't be needing them at the moment

    Now the next project... ability to sign the update.zip so recovery mode works!
    8
    The OP has been updated by me to indicate that this Exploit is intended for Gingerbread and older Android version devices. Since the OP of this thread has not officially been updated since January 2012, THREAD CLOSED until the thread owner notifies us to reopen it.
    8
    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...

    You should reboot the phone, but I didn't want to make it mandatory. I'll add a prompt asking if you want to reboot.

    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?

    Plug in a device