when i try i got this messege in the log, it looks lige the program is unable to access my system folder on the device.
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...
329 KB/s (5392 bytes in 0.016s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
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/mtdblock3
OK
Remounting system with read-write access...
OK
Pushing su...
failed to copy 'su' to '/system/bin/su': Out of memory[/COLOR]
OK
Pushing superuser.apk...
failed to copy 'superuser.apk' to '/system/app/superuser.apk': Out of memory
OK
chmod su...
Unable to chmod /system/bin/su: No such file or directory
OK
Remounting system with read-only access...
OK
Device was not rooted!
FAILED
THREAD CLOSED
ask ur question in the Q & A Thread or the 1 click thread
kongen1280 said:
when i try i got this messege in the log, it looks lige the program is unable to access my system folder on the device.
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...
329 KB/s (5392 bytes in 0.016s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
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/mtdblock3
OK
Remounting system with read-write access...
OK
Pushing su...
failed to copy 'su' to '/system/bin/su': Out of memory[/COLOR]
OK
Pushing superuser.apk...
failed to copy 'superuser.apk' to '/system/app/superuser.apk': Out of memory
OK
chmod su...
Unable to chmod /system/bin/su: No such file or directory
OK
Remounting system with read-only access...
OK
Device was not rooted!
FAILED
Click to expand...
Click to collapse
Try rooting with the unrevoked setting
howabout try use the "1-click" instead of fiddeling with ADB?
http://forum.xda-developers.com/showthread.php?t=761507
Related
Guys, i am currently at recovery mode and I need to know a way to put files in my SD card from there?
How do I accomplish that?
Do you have a sdcard reader?
To poor/cheap for that option,
http://forum.xda-developers.com/showthread.php?t=531310
console -> ums_enable
What recovery are you using? Can you put info in your signature about your hardware? It makes it a lot easier for people to help you, and you'll get help a lot faster. Like mine.
go to www.google.com and search "mount g1 through console"
the first result is an xda thread with your answer
Okay..
In order to use the console, I have to enable adb shell which I can't due to the following error message:
C:\Documents and Settings\Jonathan>adb shell
* daemon not running. starting it now *
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
misdirection said:
In order to use the console, I have to enable adb shell which I can't due to the following error message:
C:\Documents and Settings\Jonathan>adb shell
* daemon not running. starting it now *
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
You need an sh file in /system/bin
misdirection said:
In order to use the console, I have to enable adb shell which I can't due to the following error message:
C:\Documents and Settings\Jonathan>adb shell
* daemon not running. starting it now *
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
No you don't, do it from the phone.
SuperOneClick v1.8.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
Getting OS Version...
2.1-update1
OK
Pushing psneuter...
1078 KB/s (585731 bytes in 0.530s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
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
Running psneuter...
ROOTED
Pushing busybox...
1056 KB/s (1062992 bytes in 0.983s)
OK
chmod busybox...
OK
Getting mount path...
rootfs / rootfs ro 0 0
FAILED
tell me what is this ?? is my phone rooted ? but i think no help pls
Try the newest version of SuperOneClick at http://forum.xda-developers.com/showthread.php?t=803682
Make sure .NET Framework v2.0 or above is installed on your PC if you're on windows.
Make sure that Android drivers for your phone are properly installed.
Make sure you run SuperOneClick as administrator.
And yes use the latest version.
Quick noob question everyone, if I have an unlocked bootloader and custom recovery, am I rooted? Because busybox and superuser still aren't giving me command prompts. I'm on stock ics
Sent from my HTC PH39100 using XDA
Long story short no your not rooted but you did the hard part already just follow this guide you'll be rooted in under 2 minutes http://forum.xda-developers.com/showthread.php?t=1498003
THANKS!
Sent from my HTC PH39100 using XDA
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
MMVXIII said:
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Adb isn't set up properly or may need to ne run as administrator
Sent from my HTC PH39100 using xda premium
MMVXIII said:
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.
If you could get back to stick gb, Google zergrush root. Its a tempt root for users who still have their boot loader locked. But in your case, it should be locked.
Sent from my HTC PH39100 using XDA
jigajay said:
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.
Click to expand...
Click to collapse
All In One automatically reboots into recovery, runs the batch then responds with "device not found" after each command.
I did try what you said. I booted into bootloader, then ran the perm root from AIO, but got the same "device not found" result.
---------- Post added at 05:46 PM ---------- Previous post was at 05:10 PM ----------
After much reading, booting and rebooting, I managed to get this response from All In One:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
* server not running *
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
349 KB/s (22364 bytes in 0.062s)
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
4800 KB/s (843503 bytes in 0.171s)
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
However, no still no root. I've kept up to date with the AIO forum. Read the "under construction SuperGuide cover to cover. I have done exactly what many others have, except no joy for me. It appears I may have the only AT&T Vivid in the world that will not root.
http://forum.xda-developers.com/showthread.php?t=1529669
Flash that in boot loader. If it says update presses yes then you're back to gingerbread.
Sent from my HTC PH39100 using XDA
http://forum.xda-developers.com/showthread.php?t=1341162
Use that to root your phone. Follow instructions carefully.
Sent from my HTC PH39100 using XDA
im using stock 4.1.1 (rooted), i know batakang & joker support init.d but i prefer stock & want to mod it a little.
script manager does make few script's work, but cannot supercharge n stuff like that without init.d
i tried using the init.d enabler script but doesn't work & also pimp my rom uses the init.d enabler script so that doesn't work either.
so any1 have any ideas on how to enable init.d support for stock 4.1.1
I wrote a little guide and the required files in a .zip hosted on my Dropbox.
If you want an auto-mated Windows batch file to install it AND adbd insecured...
Use the Ext4 bat file.
im a little noob to do it manually so i tried the bat file method, which failed & here's the error,
Make sure your phone is NOT set to USB Mass Storage.
Make sure USB Debugging is enabled.
Make sure you are ROOTED before doing this.
Press any key to continue.
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
4548 KB/s (145332 bytes in 0.031s)
23 KB/s (370 bytes in 0.015s)
3896 KB/s (1867568 bytes in 0.468s)
0 KB/s (37 bytes in 1.000s)
0 KB/s (138 bytes in 1.000s)
cp: /system/xbin/busybox: No such file or directory
rm failed for /system/xbin/run-parts, No such file or directory
link failed No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/run-parts: No such file or directory
Rebooting. When it shows 'remount sucessful' it means it worked.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
my Atrix HD is rooted, made sure usb debugging is on, also tried installing busybox to system/xbin but in stock JB it only installs in system/bin so tried changing the lines with xbin to bin in "InstallerForExt4Devices.bat" but still does not work.
thanks for the help but i guess this phone is not for noobs
coldfear00 said:
im a little noob to do it manually so i tried the bat file method, which failed & here's the error,
Make sure your phone is NOT set to USB Mass Storage.
Make sure USB Debugging is enabled.
Make sure you are ROOTED before doing this.
Press any key to continue.
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
4548 KB/s (145332 bytes in 0.031s)
23 KB/s (370 bytes in 0.015s)
3896 KB/s (1867568 bytes in 0.468s)
0 KB/s (37 bytes in 1.000s)
0 KB/s (138 bytes in 1.000s)
cp: /system/xbin/busybox: No such file or directory
rm failed for /system/xbin/run-parts, No such file or directory
link failed No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/run-parts: No such file or directory
Rebooting. When it shows 'remount sucessful' it means it worked.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
my Atrix HD is rooted, made sure usb debugging is on, also tried installing busybox to system/xbin but in stock JB it only installs in system/bin so tried changing the lines with xbin to bin in "InstallerForExt4Devices.bat" but still does not work.
thanks for the help but i guess this phone is not for noobs
Click to expand...
Click to collapse
Try the busy box installer from play store.
Sent from my MotoAHD Maxx
Youngunn2008 said:
Try the busy box installer from play store.
Sent from my MotoAHD Maxx
Click to expand...
Click to collapse
i have busybox pro from Gplay also enabled adbd insecure but still no use
You need the "normal install" not the smart install
Sent from my phone.
Markyzz said:
You need the "normal install" not the smart install
Sent from my phone.
Click to expand...
Click to collapse
i always do normal install of busybox.
coldfear00 said:
i always do normal install of busybox.
Click to expand...
Click to collapse
With busy box app you can select to install it to xbin as well.
Sent from my MotoAHD Maxx
Youngunn2008 said:
With busy box app you can select to install it to xbin as well.
Sent from my MotoAHD Maxx
Click to expand...
Click to collapse
Yup. IIRC I just manually copied the files into xbin and init.d worked after that.
Sent from my phone.
Youngunn2008 said:
With busy box app you can select to install it to xbin as well.
Sent from my MotoAHD Maxx
Click to expand...
Click to collapse
when i select system/xbin installation fails, only installs in system/bin
Markyzz said:
Yup. IIRC I just manually copied the files into xbin and init.d worked after that.
Sent from my phone.
Click to expand...
Click to collapse
good for you bro, i also tried the same but no use.
im giving up on this phone, going for nexus 4
accidentally double post, sorry
Hello all,
I had unlocked my bootloader. flashed some roms (AOSP), used and thought of returning back to Stock as I wanted to test if the backed up TA can be restored successfully.
So I flashed .434 ftf, relocked the bootloader and tried to use the rooting toolkit to root.. But it is getting stuck in between as not getting any ahead further.. What should I do?
This is what all I can see:
Press any key to continue . . .
### beginüI ###
waiting for device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
transfer files to your phone part1
adb server is out of date. killing...
* daemon started successfully *
27 KB/s (442 bytes in 0.015s)
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
10 KB/s (170 bytes in 0.015s)
adb server is out of date. killing...
* daemon started successfully *
----------------------------------------------------------------------
[*] description:
1. press the button to restore the data in your phone operation.
adb server is out of date. killing...
* daemon started successfully *
Now unlock your device and confirm the restore operation.
if Restoring data is complete,
Press any key to continue . . .
----------------------------------------------------------------------
[*] description:
1. Dial *#*#7378423#*#* and select "Service tests" in your phone o
2. select "Display" in your phone operation.
* Screen is white until completion of restart
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
executing /data/local/tmp/onload.sh ...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
----------------------------------------------------------------------
[*] description:
1. push power button, so turn off the screen
2. push power button, so turn on the screen
* Repeat steps 1 and 2
----------------------------------------------------------------------
adb server is out of date. killing...
* daemon started successfully *
mandarjoshiin said:
Hello all,
I had unlocked my bootloader. flashed some roms (AOSP), used and thought of returning back to Stock as I wanted to test if the backed up TA can be restored successfully.
So I flashed .434 ftf, relocked the bootloader and tried to use the rooting toolkit to root.. But it is getting stuck in between as not getting any ahead further.. What should I do?
This is what all I can see:
Press any key to continue . . .
### beginüI ###
waiting for device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
transfer files to your phone part1
adb server is out of date. killing...
* daemon started successfully *
27 KB/s (442 bytes in 0.015s)
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
10 KB/s (170 bytes in 0.015s)
adb server is out of date. killing...
* daemon started successfully *
----------------------------------------------------------------------
[*] description:
1. press the button to restore the data in your phone operation.
adb server is out of date. killing...
* daemon started successfully *
Now unlock your device and confirm the restore operation.
if Restoring data is complete,
Press any key to continue . . .
----------------------------------------------------------------------
[*] description:
1. Dial *#*#7378423#*#* and select "Service tests" in your phone o
2. select "Display" in your phone operation.
* Screen is white until completion of restart
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
executing /data/local/tmp/onload.sh ...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
----------------------------------------------------------------------
[*] description:
1. push power button, so turn off the screen
2. push power button, so turn on the screen
* Repeat steps 1 and 2
----------------------------------------------------------------------
adb server is out of date. killing...
* daemon started successfully *
Click to expand...
Click to collapse
Have you usb debugging checked along with unknown sources ?
mileyxperia said:
Have you usb debugging checked along with unknown sources ?
Click to expand...
Click to collapse
Yes bro.. it has already been checked... :crying:
I can tell you it can not be related to your TA restore.
mandarjoshiin said:
Yes bro.. it has already been checked... :crying:
Click to expand...
Click to collapse
Flash again via flashtool full wipe root it with flashtool or binarys tool ?? Try to reinstall drivers ? Reboot pc ?
I reinstalled the drivers and now it has worked fine.. Now I can go ahead and try n see if restore TA works.. :fingers-crossed:
mandarjoshiin said:
I reinstalled the drivers and now it has worked fine.. Now I can go ahead and try n see if restore TA works.. :fingers-crossed:
Click to expand...
Click to collapse
Good luck flashing ta is risky could brick device :laugh: