[APP]SuperOneClick v2.3.3 - Motorola Exploit Added!
- Thread starter CLShortFuse
- Start date
- Status
Would someone please clear this up for me?
(Phone Sprint HTC Hero CDMA with 2.31.651.7)
This app's will set:
Root = S-Off? (Nand unlocked)
Un-Root = S-On (Back to complete unroot?)
Just don't want to root my friends phone and have them not be able to set it back to S-On if anything should happen to their phone.
Thanks.
(Phone Sprint HTC Hero CDMA with 2.31.651.7)
This app's will set:
Root = S-Off? (Nand unlocked)
Un-Root = S-On (Back to complete unroot?)
Just don't want to root my friends phone and have them not be able to set it back to S-On if anything should happen to their phone.
Thanks.
Last edited:
It Seems to have worked fine for me. I am using a plain old o2 locked galaxy on 2.2. I First tried TGA_Gunmans one click unlock and that failed to install update.zip due to unrecognised signature. This superoneclick though seems to have worked ? I asked it to do a test and it has been sat on "Running a SU test... " for a while, it asked me to click allow but I had no option or popups asking me to click "allow"
Code:
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...
19 KB/s (5392 bytes in 0.267s)
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...
ROOTED
Getting mount path...
/dev/block/stl9
OK
Remounting system with read-write access...
OK
Pushing su...
223 KB/s (26264 bytes in 0.115s)
OK
chmod su...
OK
Pushing Superuser.apk...
557 KB/s (196521 bytes in 0.344s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Last edited:
ok so even though the app appeared to have been waiting for a process SU test to end the device is rooted. I have installed and tested a couple of screen grab apps (both require root) and they worked fine so this does suggest the device was rooted fine.
I then thought I would test the unroot function...
Based on the above it's as if the unroot function removed superuser.apk then it tries to remove it again but because it already has it just hangs. If I unplug the phone I get and instant message to say failed which shows it is still incommunication with the phone but then fails straight away on the next step to remount with read only access. Because of this the phone isn't getting unrooted (I confirmed this by installing rooted apps again and they still work
Not sure if these sort of errors have been corrected in an upcoming revision?
Could I suggest a couple of additions. Could you do a search for the apk and only attempt to delete if exists it appears like your maybe issuing the delete command regardless as to whether the file exists or not?? Also any chance you could add a reconnection timer if the devise is disconnected for any reason. Say for example if unplug my phone it pops if with a 30 second countdown to allow you to reconnect the phone?
And finanly I would like to say thanks for the app it does work just the odd bug needs worming out then there will be donations flying from my direction
I then thought I would test the unroot function...
Code:
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...
10 KB/s (5392 bytes in 0.485s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/stl9
OK
Remounting system with read-write access...
OK
Removing su...
OK
Removing Superuser.apk...
OK
Removing Superuser.apk...Based on the above it's as if the unroot function removed superuser.apk then it tries to remove it again but because it already has it just hangs. If I unplug the phone I get and instant message to say failed which shows it is still incommunication with the phone but then fails straight away on the next step to remount with read only access. Because of this the phone isn't getting unrooted (I confirmed this by installing rooted apps again and they still work
Code:
Removing Superuser.apk...
Failure
OK
Remounting system with read-only access...
error: device not found
FAILEDNot sure if these sort of errors have been corrected in an upcoming revision?
Could I suggest a couple of additions. Could you do a search for the apk and only attempt to delete if exists it appears like your maybe issuing the delete command regardless as to whether the file exists or not?? Also any chance you could add a reconnection timer if the devise is disconnected for any reason. Say for example if unplug my phone it pops if with a 30 second countdown to allow you to reconnect the phone?
And finanly I would like to say thanks for the app it does work just the odd bug needs worming out then there will be donations flying from my direction
Last edited:
Help!!! Please!!!!
Hello guys! Is anybody can help the girl????
I need to root my Samsung Intercept 2.1 to use wifi tethering then (barnacle for ex).
I tried rooting with super one click root but got some issues.
1.After rooting procedure it says that I've rooted successfully my phone and asking to test. I suppose to see (and allow) superuser pop- up but I see nothing!!!!!
2. Checking barnacle, works fine!
3. Rebooting my phone.
4. Barnacle doesn't work (permission denied), terminal emulator says the same permission denied.
Can anybody explain that???? Did I get shell root or something like that??????
How to get full root????
Hello guys! Is anybody can help the girl????
I need to root my Samsung Intercept 2.1 to use wifi tethering then (barnacle for ex).
I tried rooting with super one click root but got some issues.
1.After rooting procedure it says that I've rooted successfully my phone and asking to test. I suppose to see (and allow) superuser pop- up but I see nothing!!!!!
2. Checking barnacle, works fine!
3. Rebooting my phone.
4. Barnacle doesn't work (permission denied), terminal emulator says the same permission denied.
Can anybody explain that???? Did I get shell root or something like that??????
How to get full root????
I didn't receive the pop-up as well but the root work for me. I try with Adfree. I just close the program when the "send test message" appears.
Did u receive "OK" in all the steps?? Maybe something went wrong...
FOR THOSE GETTING THE DBA 'version' NOTICE:
There is an xda article about the out of date article. It suggests killing the adb server manually, and restarting it:
> adb kill-server
> adb start-server
You can test by asking for the connected devices list:
> adb devices
I don't have the page open, but it should be easy to find
There is an xda article about the out of date article. It suggests killing the adb server manually, and restarting it:
> adb kill-server
> adb start-server
You can test by asking for the connected devices list:
> adb devices
I don't have the page open, but it should be easy to find
Last edited:
Trying to Root Stock (unlocked) HTC Legend from Ubuntu MM
ADB in place with little problems. I can adb start-server, kill-server and devices
- Note that sometimes I can only get results in adb devices if I use htc sync mode (thought I can change that once adb sees the device)
Phone firmware version is 2.1, recently factory reset.
the root process always stalls at:
Do you think I could be getting a permissions problem as a result of a Mono problem?
I searched this thread and didn't find any other issues.
ADB in place with little problems. I can adb start-server, kill-server and devices
- Note that sometimes I can only get results in adb devices if I use htc sync mode (thought I can change that once adb sees the device)
Phone firmware version is 2.1, recently factory reset.
the root process always stalls at:
Do you think I could be getting a permissions problem as a result of a Mono problem?
I searched this thread and didn't find any other issues.
MUST have drivers installed - Not necessarily true
There have been some other issues to the driver issue (which is not an options for some users - such as linux users.
You'll know that you're good if command line:
>adb devices
gives you a response.
In the case of my HTC legend I had to switch the USB mode to sync, run that command, and then I got a connections; after this I could switch USB mode and still get past the 'waiting for device' stage.
* Note that at the time of this post I am still not able to complete the process,but I get past this stage, and get past the rage copy stage.
So it doesn't explicitly say it and there are many noobs (me
At least this was the case for my Fascinate.
There have been some other issues to the driver issue (which is not an options for some users - such as linux users.
You'll know that you're good if command line:
>adb devices
gives you a response.
In the case of my HTC legend I had to switch the USB mode to sync, run that command, and then I got a connections; after this I could switch USB mode and still get past the 'waiting for device' stage.
* Note that at the time of this post I am still not able to complete the process,but I get past this stage, and get past the rage copy stage.
Hey guys, I ran this to try and root my TMobile G1/HTC Dream and it said my phone was rooted. It asked if I wanted to run a test so I clicked Yes. It then said Test Failed, FAILED! Is my phone not rooted and something just glitched or is my phone actually rooted?
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
720SuperOneClick
FOR ANDROID GINGERBREAD AND EARLIER DEVICES
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
- Acer Liquid Metal
- Dell Streak
- HTC Magic (Sapphire) 32B
- HTC Bee
- LG Ally
- Motorola Atrix4G
- Motorola Charm
- Motorola Cliq
- Motorola Droid
- Motorola Flipside
- Motorola Flipout
- Motorola Milestone
- Nexus One
- Samsung Captivate
- Samsung Galaxy 551 (GT-I5510)
- Samsung Galaxy Portal/Spica I5700
- Samsung Galaxy S 4G
- Samsung Galaxy S I9000
- Samsung Galaxy S SCH-I500
- Samsung Galaxy Tab
- Samsung Transform M920
- Samsung Vibrant
- Sony Ericsson Xperia E51i X8
- Sony Ericsson Xperia X10
- Sprint Hero
- Telus Fascinate
- Toshiba Folio 100
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
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:
20For 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
8
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.
Plug in a device
New posts
-
-
Question SAMSUNG S22 ULTRA NEED HELP PLZ!!!!!!!!!!!!!!!
- Latest: nguyenlucky
