[Q] SuperOne Click Error! - Android Q&A, Help & Troubleshooting

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\Root\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\Root\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\Root\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? :/

josecleocir said:
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\Root\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\Root\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\Root\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? :/
Click to expand...
Click to collapse
As it says you have not enough space on your device
Sent from my X8 using xda premium

Please use the Q&A Forum for questions Thanks
Moving to Q&A

Related

HELP, I've lost root!

HELP ME, I've lost root!
I ran the X10root v 1.0.8 although i already had root and now i lost root. (X10i 2.1 nordic)
If i try to root it again with the SuperOneClick thing i get the following:
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...
526 KB/s (5392 bytes in 0.010s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock2
OK
Remounting system with read-write access...
OK
Pushing su...
failed to copy 'su' to '/system/bin/su': Permission denied
OK
Pushing superuser.apk...
2628 KB/s (196521 bytes in 0.073s)
OK
chmod su...
OK
Remounting system with read-only access...
OK
Device was not rooted!
FAILED
Click to expand...
Click to collapse
Please, help me.
EDIT:
Maybe this is also relevant: (adb shell)
# su
su
reloc_library[1245]: 3654 cannot locate '_ZNK7android6Parcel15setDataPositionEj'...CANNOT LINK EXECUTABLE
#
Click to expand...
Click to collapse
2.1 or 1.6?
X10i 2.1 nordic
theeedy said:
X10i 2.1 nordic
Click to expand...
Click to collapse
Factory reset....
:/
Sent from my X10i using XDA App
Try again - http://forum.xda-developers.com/showthread.php?t=824788
I tried it already around 10 times.
EDIT: I had to reflash the firmware -.-

[Q] Rogers 2.2 SuperOneClick problems

Hey everyone!
Ive decided to go with SOC because Im not confident to do anything else deeper yet.
Ive been having some trouble with it working. Ive gone to the following places:
http://forum.xda-developers.com/showthread.php?t=993321&highlight=SuperOneClick
http://forum.xda-developers.com/showthread.php?t=982029&highlight=SuperOneClick
http://forum.xda-developers.com/showthread.php?t=972235&highlight=SuperOneClick
When I just plugged it in and tried it this is the result:
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.11s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.14s
Waiting for device...
OK 0.09s
2.2.1
Getting manufacturer...
Dell Inc.
OK 0.05s
Getting model...
Dell Streak
OK 0.03s
Getting version...
14896
OK 0.03s
Checking if rooted...
False
OK 0.09s
Installing BusyBox (temporary)... - Step #1
1619 KB/s (1062992 bytes in 0.641s)
OK 0.75s
Installing BusyBox (temporary)... - Step #2
OK 0.04s
Rooting device... - Step #1
1629 KB/s (585731 bytes in 0.351s)
OK 0.46s
Rooting device... - Step #2
OK 0.04s
Rooting device... - Step #3
OK 0.02s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 0.05s
Rooting device... - Step #5
error: protocol fault (no status)
FAILED
When I tried turning off the phone, plugging it in, starting SOC and then turning the phone on when It says waiting for device:
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.14s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.16s
Waiting for device...
OK 26.09s
2.2.1
Getting manufacturer...
Dell Inc.
OK 0.03s
Getting model...
Dell Streak
OK 0.03s
Getting version...
14896
OK 0.03s
Checking if rooted...
False
OK 0.07s
Installing BusyBox (temporary)... - Step #1
3223 KB/s (1062992 bytes in 0.322s)
OK 0.43s
Installing BusyBox (temporary)... - Step #2
OK 0.03s
Rooting device... - Step #1
3091 KB/s (585731 bytes in 0.185s)
OK 0.29s
Rooting device... - Step #2
OK 0.02s
Rooting device... - Step #3
OK 0.02s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 0.03s
Rooting device... - Step #5
OK 8.09s
Remounting /system with read-write access...
error: closed
FAILED
Im going to try an earlier version of SOC. I will check back here a little later with results. Thanks in advance!
I HAVE ANSWERED MY OWN QUESTION / PROBLEM!!!!!!!!!!!!!!!!!!!!!!
I ran SOC 1.7 and it was fine. I just had to.......
Turn phone off.
Start SOC 1.7.
clicked rageagainstthecage
clicked root
saw this:
SuperOneClick v1.7.0.0
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...
1053 KB/s (5392 bytes in 0.005s)
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
Pushing busybox...
2227 KB/s (1062992 bytes in 0.466s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock6
OK
Reading OS Version properties...
Version: 2.2.1
OK
Remounting system with read-write access...
OK
Pushing su-v2...
777 KB/s (26264 bytes in 0.033s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1230 KB/s (196521 bytes in 0.156s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
and BAM Im rooted!
Thank God for this forum !!!

Root + Unroot

Hi,
I tried root with DoomLord's script and also with unlockroot.com, both failed
I need an easy way to root and also unroot
System version is 65.1.21.XT910.Retail.en.il
Thanks!
Unzip to disk с:\, run run.bat.
Wait until the end.
Enjoy
Yes, I have this
But before I try I want to know what is the unrooting method for this
Thanks
mickeycohen said:
Yes, I have this
But before I try I want to know what is the unrooting method for this
Thanks
Click to expand...
Click to collapse
With the motofail root method, on the xt912 at least, doomlords unroot method worked when I tried it.
Sent from my DROID RAZR using xda premium
I have the xt910. Anyone has any idea if it will also work? I need anything to unroot except factory reset
mickeycohen said:
I have the xt910. Anyone has any idea if it will also work? I need anything to unroot except factory reset
Click to expand...
Click to collapse
To do it is not possible,will only reset!
OK, so here is the full story. My RAZR is the XT910 running on 2.3.5
I made sure I have the most updated motorola drivers, phone is connected via USB on Charge Only, USB Debugging and Unknown Sources enable
unlockroot - recognizes the phone but fails to root, first error says: "failed to chmod file :/data/local/tmp" and then "failed to get shell root"
DoomLord fails:
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
625 KB/s (23060 bytes in 0.036s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
1478 KB/s (1075144 bytes in 0.710s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
142 KB/s (439 bytes in 0.003s)
df: /mnt/secure/asec: Permission denied
df: /mnt/sdcard/.android_secure: Invalid cross-device link
--- Free space on /system : 15230 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
I have not tried the motofail option because I am not sure how to Unroot. I did however find this:
http://forum.xda-developers.com/archive/index.php/t-1492965.html
Please help...
Thanks
Had the same problem yesterday,
Roted with winfail,
then tryed to unroot using doomlord.
both of them worked for me on OTA 2.3.6 version
Check out this program. http://bit.ly/HoXqYg
I used it to root my phone (on 2.3.6, and 2.3.5). Never tried unrooting, but rooting and install safestrap worked well for me.

[Q] Root for Samsung Galaxy Exhibit 4g (Exhibit II 4G) 2.3.6???

Does anyone know a way to root this device running on 2.3.6? Zerg Rush isn't working?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I too have this question, as I'm actively searching for results on how to root this device. I just purchased it today from T-Mobile and came pre-loaded with 2.3.6. So far ZergRush is non-functional.
Code:
---------------------------------------------------------------
Easy rooting toolkit (v3.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
2046 KB/s (23056 bytes in 0.011s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00029118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2391 KB/s (1075144 bytes in 0.439s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Code:
Model Number : SGH-T679
Android Version : 2.3.6
Baseband version : T679UVLE1
Kernel version : [email protected] #3
Build number : GINGERBREAD.UVLE1
If anyone needs anything else, lemme know. I'll post what I can. :\
-------
Ok. Wow. That was brilliantly easy. Apologies for that. xD;
Followed the instructions given from : http://forum.xda-developers.com/showthread.php?p=26859816
Installed the kernel.
I am now rooted on 2.3.6. Thank you SO much! <3
kdz?
Will removing KDZ updater still remove the OTA push notification? Last time I had to do this was with an SGH-T839 on froyo. Keeping root & touchwiz is in my best interests...
http://forum.xda-developers.com/showthread.php?t=1686384
Not working
hey i tryed it and nothing happen i waited around like twenty mins...am running ginger bread 2.3.6 unrooted i in stall the driver ran the zergRush exploit and it only said;
daemon not running,
starting it now,
daemon successfully started,
and nothing after that
This didn't work. However, a couple of virus software programs did tell me that it was dangerous. And then I started to have popups and my browser started to act funny. Hummmm...

[Q] Tablet P rooting

I use AiO tool on Tablet P Android 3.2.1
and this is error I'm getting. Any idea what's wrong?
Thanks Much!!!
>>>>>>>>>>>>
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'files\su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
failed to copy 'files\tempsu' to '/system/bin/tempsu': Read-only file system
Unable to chmod /system/bin/tempsu: No such file or directory
Unable to chmod /system/bin/tempsu: No such file or directory
failed to copy 'files\busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'files\Superuser.apk' to '/system/app/Superuser.apk': Read-only f
ile system
[*] Cleaning up...
<<<<<<<<<<<<<<<<<<<<<<
Driver seems to be OK:
>>>>>>>>>>>>>>>>>>>
C:\Users\shlasasha\Desktop\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
4507046411fb2d7 device
<<<<<<<<<<<<<<<<<<<<<
What this means?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[*]*************[*]
[*] ADB Shell [*]
[*]*************[*]
Type EXIT to get out of shell
$ devices
devices
devices: permission denied
$
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
what kernel version you got?
is it build10?
weaponXandroid said:
what kernel version you got?
is it build10?
Click to expand...
Click to collapse
2.6.36.3
[email protected] #1
Additional info:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[*] Attempting to move system package library directory...
[+] System package com.android.providers.media has uid 10035
[+] Flooding log...
run-as: Package 'com.pwn.me' is unknown
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Does it mean I'm missing something?
Thanks!
Tried this thread:
http://forum.xda-developers.com/showthread.php?t=1487020
got the same error
also run Run.bat from here manually line by line with the same effect.
another try of this thread:
http://forum.xda-developers.com/showthread.php?t=1887447
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
C:\PhonesAndTablets\SonyP\Xperia_Tablet_Root>adb restore settings.ab
adb: unable to connect for backup
<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Google says it required ICS. is it really? I'm 3.2.1 and I didn't get Restore button on the device.
HELP:silly:
Got it !!!
There is another setting under "Applications->Development" "Allow mock locations"
It is not mentioned in any guides.
After I set that one ALLinONE worked.
Thanks everyone!!!

Categories

Resources