SuperOneClick
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
No comments:
Post a Comment