Database Users

Terminal Emulator: System Access from Phone

I am using Terminal Emulator on the phone (because my PC is screwed up). I am trying to copy a directory from the sd card to /system/media/audio directory on the ROM.
I am able to get rw access to the ROM by typing in..
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
then I am trying to copy the file by typing..
cp -r /sdcard/download/ringtones /system/media/audio
It gives me an error saying "Cannot allocate system memory"
does anybody know what that means? How can do this?

you can't copy across mount points. At least, I think that may be what's happening.

You cant write to system from a droid itself....need to use recovery

problem with adb push

i get an error when try adb push a recovery file to my sdcard and ideas?

Need to give it a file name at the location you're moving it to I believe.
Example: adb push foo.txt /sdcard/foo.txt

ok thanx, how do i delete a file off the phone? when i install a custom recovery and reboot it goes back too stock recovery so i need to delete /system/etc/install-recovery.sh file, but need to know how

corolla90 said:
ok thanx, how do i delete a file off the phone? when i install a custom recovery and reboot it goes back too stock recovery so i need to delete /system/etc/install-recovery.sh file, but need to know how
Click to expand...
Click to collapse
enter this into command prompt or terminal
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh

Help to get a custom ROM an a rooted HTC Magic

Hi everyone,
I am kind of stuck with getting a custom ROM on my HTC Magic 32B (spl:1.33.0013 radio:2.22.28.25 os:2.2.1ota)
I cant flash custom recovery...or anything else
Here´s what happend so far:
http://forum.xda-developers.com/showthread.php?t=939749
Hope someone can help

There was another person that I was working with having the same problem. For whatever reason we couldn't get the custom recovery to stick no matter what we tried and we ended up stopping with him trying to downgrade to root. I'm not sure where he got. You can try using "flash_image" from terminal, but it probably won't help. Download the attached "Flash_image.zip", unzip the file, and put in on the root of your SD card. Then open up terminal on the phone and type the following hitting enter at the end of each line:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/*name of recovery*.img
reboot recovery

Thanks for your instructions...but it did not work for me.
I kind of gave up on getting my Magic flashed.

Did you check to see if there are any scripts that will override the recovery on closure?
Do this:
Pull out the battery when you execution of the flash_image command has succeeded.
This way you can avoid any scripts being executed on turn-off.
Now try to see if you can get the custom recovery to work!

Terminal command help remount help

I have an Atrix on AT&T. Which means there's a bootloader encryption, and the carrier prevents non-market apk installations, which I have resolved since my phone is rooted and I have changed the boot animation already.
In order to do these things, I found Ghost Commander that would let me chmod my system directories...which is fine, but I feel kind of gimped that I can't do it on terminal.
Basically, what I want to be able to do is remount /system as rw using terminal.
This method doesn't work on both terminal and emulator on my phone. I have done:
Terminal:
Code:
sudo su
cd [sdk directory]
./adb devices
./adb shell
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system
and this is where I get stuck because I just get an Invalid argument error.
Here is some info about my sytem -
Usage: mount [-r] [-w] [-o options] [-t type] device directory
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime, data=ordered 0 0
Been searching for the answers for a while now, and now I'm here. What am I doing wrong? Thanks

there
Code:
mount -o remount,rw /dev/mmcblk0p12 /system
back
Code:
mount -o remount,ro /dev/mmcblk0p12 /system

Hmm, well at least I didn't get any errors this time.
I didn't get a confirmation or that it did anything at all. Is that normal?

Run mount with no parameters and look for the line with that device name, should see rw in that line instead of ro.
Sent from my MB860 using XDA App

Thanks guys, but I resorted to busybox chmod command instead lol

I tried this and got no errors, and using cat /proc/mounts/ I see the path as rw. But when I try to copy I still get the read only file system error.
**Lol, I had the phone in usb storage mode and had to switch it to Windows Media Sync**

Copying Vending.apk - Can't 'cp' after running SU

I am trying to move the vending.apk into system/app from the command line.
I was going to use ES File manager. However, when I try to do 'root explorer' it fails. I do still believe I have a working root because SU works from the adb shell..
Here is what is driving me crazy, I can't seem to move or copy the file from the adb shell after I root and mount the folder as read/write.
I run these commands to set permissions and mount it read/write.
SU
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
However after running SU it returns 'cp not found' when I try to run cp to copy the file. Example...
# cp /mnt/sdcard/Vending.apk /sytem/appVending.apk
cp: not found
If I try to move it, it returns this error.
# mv /mnt/sdcard/Vending.apk /system/app/Vending.apk
failed on '/mnt/sdcard/Vending.apk' - Cross-device link
Is there something else I need to do to move or copy after running SU?

You would first have to fix the mount command because it's not a yaffs2 filesystem, and it's not /dev/block/mtdblock3. The correct command should be "mount -o remount,rw -t ext4 /dev/block/mmcblk0p9". Then try to copy it over to /system/app.
If it still fails, you can adb push it to /system/app after having mounted the partition in read/write.

i just moved it with explorer myself

Try to rename it from .apk to .jpg and copy it with ES File Manager. If it's successful rename it back to .apk after it's in /system/app.