though I did use this help too(since I am on bell)
Quote:
hat worked for me Bell I9000M JK4 or JL2 was to:
Disconnect Phone
Enable USB Debugging Mode
Shut Down Phone
Open SuperOneClick
Press ROOT
Wait until you see "Waiting for Device"
Connect Phone, wait for battery charging graphic
Turn On Phone
Let it do its thing, it should work all the way until you get SuperUser pushed to your device
If you get an USB error, try again from the start using another port
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
This is impossible! There's no way to do that fast enough on my Droid and computer. I can't get away from looping and this solution will not work.
Do I have to be in download mode when I hook up my phone to the computer?
Do I start the Superone click GUI before hooking the phone to the computer?
Can someone post a short step by step?
Thanks alot.
Here is all I get:
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
is there a solution for this? i tried checking and unchecking debug mode but it ddint work either.
i cant open file!!! I think the file corrupted. I really need help.
Quote:
Originally Posted by clshortfuse
superoneclick
i made it. I tested it. It works.
Here's a one-click root that works with froyo on our captivates. It's not just the captivate. It works with almost all phones and all android versions. (including the i9000, droid, nexus one)
the program requires microsoft .net framework 2.0+ or mono v1.2.6+
operations systems with native support:
for more information about making it work in linux:
See here
you need to put your phone on usb debugging mode and 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)
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
compatibility list
please note that if you device is not listed here, it doesn't automatically make it incompatible. The list is definitely incomplete
nexus one
samsung galaxy s i9000
samsung captivate
samsung vibrant
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.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:
i was just waiting until somebody make some usefull tool, one click and thatīs all, and the best, u can un-root ur phone like nothing happend!
Well, until, XD, some problems happend!
All works great, my phone was rooted, i can use superuser, and i can use some apps like setcpu... etc.
Well, i was using setcpu, until the next time that i try to open this app, and appears the message, that i need root permission... that i lost my root permissions? if i open super user, it show me that SetCpu itīs allowed to run without problem... but it doesnīt!
Well i was thinking, maybe its the app, so i installed another one, for screenshot, work good the first time, then i close it, opened again, and the next picture say, that i not allowed because iīm not root user...
If the root access work at the first time, why it doesnīt now? I restart my phone, but nothing.
Worked for me on Nexus One after resolving an issue with W7 64bit drivers - had to install App Inventor to get hold of the drivers first.
Thanks very much - donation in your mailbox
I have a samsung Captivate 2.1 On Windows 7 x64 with Admin. I keep getting this error = FAILED on Allow Non Market Apps
I have the phone rooted, but this won't seem to work. I followed the instructions to help solve the loop issue and still gives me FAILED
Any Help
Thanks
Code:
***Requires root permission! Watch your phone to allow Superuser commmands***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting mount path...
/dev/block/stl9
OK
Checking for sqlite3
Pushing sqlite3...
102 KB/s (24120 bytes in 0.230s)
OK
chmod sqlite3...
OK
Getting settings.db location...
/data/data/com.android.providers.settings/databases/settings.db
OK
Checking value... (requires root)
Non-market applications are disabled.
Allow non-market apps... (requires root)
OK
Checking value... (requires root)
FAILED
XDA Developer TV Producer Jayce released a video a … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?
Introducing XDA:DevCon A Conference For Developers By Developers
>
[APP]SuperOneClick v2.3.3 - Motorola Exploit Added!
Print
Email
View Profile
View Forum Posts
SuperOneClick is Hanging
Linear Mode
