Problem pushing files to phone

[Guest 843]

I tried copying files to the system folder but I keep getting "failed to copy, out of memory". Any idea why? I also tried using Root Explorer but despite the pasting animation being displayed, the files were not copied.

I've tried both the terminal emulator

$ su

# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system

# cp /sdcard/libt9.so /system/lib

and adb

adb remount

adb push lib/libt9.so /system/lib/libt9.so

It seems the file has been moved successfully through recovery mode, but I still can't see the file when the phone is booted.

[Guest woti17]

I tried copying files to the system folder but I keep getting "failed to copy, out of memory". Any idea why? I also tried using Root Explorer but despite the pasting animation being displayed, the files were not copied.

....

because /system is readonly, despite of what you do or root explorer says

you need either be in recovery or have s-off to write to /system

Edited November 3, 2010 by woti17

[Guest 843]

because /system is readonly, despite of what you do or root explorer says

you need either be in recovery or have s-off to write to /system

I did it through recovery (the transfer time was shown) but oddly, the file still isn't in the phone.

[Guest woti17]

I did it through recovery (the transfer time was shown) but oddly, the file still isn't in the phone.

does the output of mount command show any error?

what does

adb shell mount

(system rw?) show

and

adb shell ls -l /system

(does it contain the full directories or only bin and lib?)

[Guest 843]

D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>adb shell mount

- exec '/system/bin/sh' failed: No such file or directory (2) -


D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>adb shell ls -1 /system

- exec '/system/bin/sh' failed: No such file or directory (2) -

Edited November 3, 2010 by 843

[Guest woti17]

D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>adb shell mount

- exec '/system/bin/sh' failed: No such file or directory (2) -


D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>adb shell ls -1 /system

- exec '/system/bin/sh' failed: No such file or directory (2) -

your system is not mounted correctly (contains no sh command) so you have no shell and can't remount rw the nand system partition

try recovery-windows.bat on pc first

and then

adb remount

adb shell

cd /system/bin

ls -l ("el" not "one")

you should see a lot of commands like mount, sh ....

exit

adb shell mount /system -o remount,rw

then push your files again with adb push

Edited November 3, 2010 by woti17

[Guest 843]

Following recovery, I was able to boot into Clockwork Recovery (I wasn't able to) but I still have this problem.

Here's what happened when I tried normal recovery.

D:\>cd Recovery\Backup\Android\Root\android-sdk-windows\tools


D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>adb remount

remount failed: Invalid argument


D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>adb shell

- exec '/system/bin/sh' failed: No such file or directory (2) -


D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>cd /system/bin

The system cannot find the path specified.


D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>ls -l

'ls' is not recognized as an internal or external command,

operable program or batch file.


D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>adb shell mount /syste

m -o remount,rw

- exec '/system/bin/sh' failed: No such file or directory (2) -


D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>

Here's what happened when I used Clockwork.

D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>adb remount

remount failed: Unknown error: 0


D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>adb shell

~ # cd /system/bin

cd /system/bin

/sbin/sh: cd: can't cd to /system/bin

~ # ls -l

ls -l

drwxrwx--x	1 system   cache		 2048 Nov  3 14:19 cache

drwxr-xr-x	2 root	 root			 0 Nov  3 14:19 data

drwxr-xr-x	2 root	 root			 0 Nov  3 14:19 datadata

-rw-r--r--	1 root	 root		  4205 Jan  1  1970 default.prop

drwxr-xr-x   12 root	 root		  1540 Nov  3 14:19 dev

drwxr-xr-x	2 root	 root			 0 Nov  3 14:19 etc

-rwxr-x---	1 root	 root		107496 Jan  1  1970 init

-rwxr-x---	1 root	 root		   776 Jan  1  1970 init.rc

dr-xr-xr-x   51 root	 root			 0 Jan  1  1970 proc

drwxr-xr-x	4 root	 root			 0 Nov  3 14:19 res

drwx------	2 root	 root			 0 Mar  8  2010 root

drwxr-xr-x	2 root	 shell			0 Nov  3 14:19 sbin

drwxrwxrwx	2 root	 root			 0 Nov  3 14:19 sd-ext

drwxr-xr-x	2 root	 root			 0 Nov  3 14:19 sdcard

drwxr-xr-x   17 root	 root			 0 Jan  1  1970 sys

drwxr-xr-x	2 root	 root			 0 Nov  3 14:19 system

drwxr-xr-x	2 root	 root			 0 Nov  3 14:19 tmp

~ # exit

exit


D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>adb shell mount /syste

m -o remount,rw

mount: can't find /system in /proc/mounts


D:\Recovery\Backup\Android\Root\android-sdk-windows\tools>

Edited November 3, 2010 by 843