i've read and read still can't find anything revelant to my issue
Killing ADB Server...
* server not running *
Done..
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Done..
Waiting for device...
Done..
Pushing rageagainstthecage...
150 KB/s (5392 bytes in 0.035s)
Done..
chmod rageagainstthecage...
Done..
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock3
OK
Remounting system with read-write access...
Done..
Pushing su...
failed to copy 'C:\Users\\Desktop\root me\su' to '/system/bin/su': No space left on device
Done..
chmod su...
Unable to chmod /system/bin/su: No such file or directory
Done..
Pushing Superuser.apk...
cannot stat 'C:\Users\\Desktop\root me\Superuser.apk': No such file or directory
Done..
Remounting system with read-only access...
Done..
Running a SU test...
Test failed!
FAILED
My phone models: sharp 003SH
Use superoneclick v1.9.1 root, problems.
SuperOneClick v1.9.1.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
Getting OS Version...
2.2
OK
2.2
Pushing psneuter...
1906 KB/s (585731 bytes in 0.300s)
OK
chmod psneuter...
OK
Running psneuter...
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 psneuter...
ROOTED
Pushing busybox...
2011 KB/s (1062992 bytes in 0.516s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock5
OK
Remounting system with read-write access...
OK
Pushing su-v2...
failed to copy 'F:\SuperOneClickv1.9.1\Root/su-v2' to '/system/bin/su': Out of memory
OK
chmod su...
Unable to chmod /system/bin/su: No such file or directory
OK
Pushing Superuser.apk...
failed to copy 'F:\SuperOneClickv1.9.1\Root/Superuser.apk' to '/system/app/Superuser.apk': Out of memory
OK
Creating /system/xbin...
mkdir failed for /system/xbin, Out of memory
OK
Checking for busybox
Remounting system with read-only access...
OK
Running a SU test...
Test failed!
FAILED
Detailed information: sharp softbank 003SH
System: Android2.2
Someone also met me this question?
Nobody will?
I'm needing root so I can figure out what APN my 005SH connects to so I can use its SIM card. Can you at least see your APN info on your 003SH since they're sisters?
Well, I would personally try GingerBreak and not bother with this one.
Please pose in pre existing thread http://forum.xda-developers.com/showthread.php?t=803682 on that note thread closed.
Hi guys when i try to unroot my lg g2x i get the following error
SuperOneClick v1.9.5.0
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing GingerBreak...
966 KB/s (16830 bytes in 0.017s)
OK
chmod GingerBreak...
chmod: no such tool
OK
Running GingerBreak...
ROOTED
Pushing busybox...
1422 KB/s (1062992 bytes in 0.730s)
OK
chmod busybox...
chmod: no such tool
OK
Getting mount path...
mount: no such tool
FAILED
how am i supposed to unroot?
please help, my root has been having a lot of issues. for example a my wifi doesn't work along with some other options on my phone.
Hey There,
I've searched ages for an answer, didn't find anything. Please help me!
Story:
I've bought an xperia mini and rooted it with the doomlord_v3 script. Everything was fine... until I accidentally uninstalled Busybox. Titannium stopped working and Bloatware is all over the place!
What I tried:
I can't reinstall Busybox, even though I still have root access. So far I've tried the following Methods:
-Running the Doomlord Script one again
-Stephen Stericson Installer
-Resetting my Phone (+erase of personal data & sd card)
=>Didn't help a bit, I still had root access and errors stayed the same
-Doomlordscript
-JRummy16 Installer
=> tells me, everything is installed, but after installation still shows: not installed
-Stephen Streicson Installer
=> want's to get root access, even though I granted su rights
-Doomlordscript
Since the accident, the Doomlordscript returns the following lines:
---------------------------------------------------------------
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
Drücken Sie eine beliebige Taste . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- pushing zergRush"
720 KB/s (23056 bytes in 0.031s)
--- correcting permissions
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- executing zergRush
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- 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
2584 KB/s (1075144 bytes in 0.406s)
--- correcting permissions
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- remounting /system
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- copying busybox to /system/xbin/
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- correcting ownership
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- correcting permissions
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- installing busybox
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- correcting permissions
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- correcting symlinks
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- rebooting
ALL DONE!!!
Drücken Sie eine beliebige Taste . . .
Click to expand...
Click to collapse
Questions:
What can i do to make busybox work again?
Is there an even harder reset (xperia mini), with the consequence, that the Phone is really in factory state and zergling rush will work again?
Where can I find an answer?
Please Help me! For you are a great hero of humanity.
was Busybox installed in the bin or xbin? ...more it seems that the system partition is read-only mode, to install you have to move it to RW (read / write) mode.
most complete reset would be reflashing a new rom.
it looks like that script "Doomlordscript" fails, because it tries to use busybox itself, the binary "sh" is part of busybox too.
So hm i would guess you could put the busybox onto your device by hand and then create all the symlinks like "sh" to "busybox sh" yourself...
google: "busybox symlink" etc.
use adb shell to copy busybox to your sdcard
Thank you for both of your replies.
I tried to make the installer install both to /xbin and /bin. When everything still worked, busybox was installed in xbin. Sorry for beeing a noob, but how do I mount the partition in RW mode?
I did root my device with the zerg exploit, but the bootloader is still locked. I am now searching for methods that don't require unlocking the bootloader. If anything fails and flashing is my last option, I will have to do it though. Does anyone of you know where to aquire an original rom to flash?
So i tried to follow Dark3n and I am now stuck here:
D:\>adb devices
List of devices attached
425839.... device
D:\>adb shell "su"
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
Since every singele tutorial/how to about installing busybox manually requires the adb shell working, I don't really know how to move on. Is there a file explorer, which doesn't require busybox and would enable me to make the needed directories?
You could just try some, "SD Maid" in my signature has an explorer.
There is root explorer, ES File explorer, etc. plenty in the market...
Don't know if they will work though, what happens if you just type "adb shell"...
D:\>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
I found a place where I can download the latest images. I've aleady tried es file explorer, but I don't see the System folder. After Starting SD Maid the following Message Comes up. I translated it from German to English, I might have chosen a formulation different from the original english Error.
Busybox error! Could not use our Busybox :-( To prevent unindended behavior SD Maid will terminate. Please try to restart SD Maid, or reinstall it.....
Click to expand...
Click to collapse
What do you mean by "our busybox" I suppose you don't have an Busybox integrated in you App.
Stupid question:
Does Flashtool require an unlocked bootloader, in oder to flash an original rom?
I have a busybox in my app, but it needs to be set up too.
Apparently basic system tools are missing to set it up.
Hm im running out of ideas here...
I think that busybox uninstaller did remove its own Shell, but not the System link. A solution would be to push a shell in the expected directory. Adb push is working. Unfortunately I don't know where to acquire the original shell, nor where to push it.
Sent from my ST15i using XDA App
Probably have to push it to /system somewhere, but you have to make system writeable i think "adb remount" should do that.
Solved
I solved the Problem by flashing my device.
I've falshed my Phone with the Flashtool. I did try it several times and encountered several errors to wich I will describe the solution here.
At first I workt in an XP environment and Flashtool didn't recognize my Phone, consequeltly t've tried to install several drivers. All failed.
In an Win 7 environment I also failed at the beginning. Flashtool did always ask me wich Phone I did connect and did not recognize it when i I plugged it in flash mode. Log:
27/028/2011 11:28:25 - INFO - Searching Xperia....
27/028/2011 11:28:25 - ERROR - Please plug you device in flash mode
27/028/2011 11:28:26 - INFO - Searching Xperia....
27/028/2011 11:28:26 - ERROR - Please install or reinstall device drivers from drivers folder
27/028/2011 11:28:27 - INFO - Device connected in flash mode
27/028/2011 11:28:27 - INFO - Searching Xperia....
27/028/2011 11:28:27 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/028/2011 11:28:28 - INFO - Searching Xperia....
27/028/2011 11:28:28 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/028/2011 11:28:29 - INFO - Searching Xperia....
Click to expand...
Click to collapse
I finally succeeded when I uninstalled all drivers related to my Phone with USB-deviewer and installed the GordonsGate drivers(you can find them in /flashtool/drivers). Then I connected my Phone in MTP-mode with debugging enabled. Flashtool did not ask to recognize my Phone as it did before, nor did it report wich Phone I connected. Still flashing worked. (With an Xperia Mini you go in flash mode by pressing the Volume Down Button). Log:
27/041/2011 11:41:52 - INFO - Searching Xperia....
27/041/2011 11:41:52 - ERROR - Please plug you device in flash mode
27/041/2011 11:41:53 - INFO - Searching Xperia....
27/041/2011 11:41:53 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:54 - INFO - Searching Xperia....
27/041/2011 11:41:54 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:55 - INFO - Device connected in flash mode
27/041/2011 11:41:55 - INFO - Searching Xperia....
27/041/2011 11:41:55 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:56 - INFO - Searching Xperia....
27/041/2011 11:41:56 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:57 - INFO - Searching Xperia....
27/041/2011 11:41:57 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:58 - INFO - Searching Xperia....
27/041/2011 11:41:58 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:59 - INFO - Searching Xperia....
27/041/2011 11:41:59 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/042/2011 11:42:00 - INFO - Searching Xperia....
27/042/2011 11:42:00 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/042/2011 11:42:00 - INFO - Start Flashing
27/042/2011 11:42:00 - INFO - VER="R9A029";DATE="20110701";TIME="12:40:00";
27/042/2011 11:42:00 - INFO - Flashing loader
Click to expand...
Click to collapse
Thank you for your Help
I am happy to check out i was of some help for you.
please help me, what is daemon? this is what I got
-----------------------------------------------------------
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 N
(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 devi
(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
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- cleaning
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing zergRush"
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- executing zergRush
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- 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
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing busybox
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- remounting /system
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- copying busybox to /system/xbin/
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting ownership
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- installing busybox
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing SU binary
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting ownership
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting symlinks
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing Superuser app
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- cleaning
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- rebooting
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
ALL DONE!!!
Press any key to continue . . .
Can anyone tell me what's the problem here?
---------- Post added at 10:10 PM ---------- Previous post was at 09:20 PM ----------
ah, i think I got it, I just rebooted my phone, thanks
It seems like your ADB drivers aren't properly installed. Ceck put this toutorial:
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Edit: Just saw everything is already fine
hey all i am new here ,
ok I unlocked the bootloader of my phone and was using the DooMLoRD tool (v4) tool but I get these errors. I restarted the pc in retried but did not work :/
Code:
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
adb server is out of date. killing...
* daemon started successfully *
mkdir failed for tmp, File exists
--- cleaning
adb server is out of date. killing...
* daemon started successfully *
rm failed for *, No such file or directory
--- pushing zergRush
adb server is out of date. killing...
* daemon started successfully *
360 KB/s (23060 bytes in 0.062s)
--- correcting permissions
* daemon not running. starting it now *
* daemon started successfully *
--- executing zergRush
adb server is out of date. killing...
* daemon started successfully *
[**] 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)
adb server is out of date. killing...
* daemon started successfully *
--- DEVICE FOUND
--- pushing busybox
1460 KB/s (1075144 bytes in 0.718s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 22524 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 . . .
this is what I got , how can this be solved
thanks