Database Info

system as read/write

need a little help here please...
I want for my /system to be mounted as read/write automaticly upon startup of the phone using this command "mount -o,remount rw /dev/block/mtdblock3 /system"
How can i make this command to be executed as ROOT when my phone starts up.
THanks

vtecpower said:
need a little help here please...
I want for my /system to be mounted as read/write automaticly upon startup of the phone using this command "mount -o,remount rw /dev/block/mtdblock3 /system"
How can i make this command to be executed as ROOT when my phone starts up.
THanks
Click to expand...
Click to collapse
Why do you need this?? Just download droidsans andwhen you need read write just use that.

I need it bc im trying to move my apps to my sd card.....if i have the /system in read only mode then the phone crashed when i try to install a new app but it works fine when my /system is read and write

I doubt you need to mount /system rw. Do ls -l in /system and make sure sd has the same owner/permissions as the other dirs and it should work.

vtecpower said:
I need it bc im trying to move my apps to my sd card.....if i have the /system in read only mode then the phone crashed when i try to install a new app but it works fine when my /system is read and write
Click to expand...
Click to collapse
i have followed the instructions in the post titled apps on sdcard and it works fine without mounting the system RW. look at that post and follow those directions.

See: http://forum.xda-developers.com/showpost.php?p=3386761&postcount=2
Just add the line to The File insted of the Path Part.
The is called after system is mounted so it should work fine

Remount system writable

just do this and you can read and write the system partition
Code:
mount -t yaffs2 -o remount,rw /dev/block/mtdblock4 /system
I have tried to remove some stock apps but am getting an error directory not empty.

l33tlinuxh4x0r said:
just do this and you can read and write the system partition
Code:
mount -t yaffs2 -o remount,rw /dev/block/mtdblock4 /system
Click to expand...
Click to collapse
Iv always seen it written like this
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system

You can also do this:
Code:
mount /dev/block/mtdblock4 /system

Ummm isnt it nand locked?
What is this? Is this real life?

Jus10o said:
Iv always seen it written like this
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
Click to expand...
Click to collapse
They're both the same, you're setting the type of filesystem and then what options and then pointing to what to mount. They are just written differently. And although I know the simplest things are overlooked, but I'd have figured toast and company would of tried mounting the filesystem already. Feel free to correct me if I'm wrong and if anyone can validate this.

Obama's>god said:
Ummm isnt it nand locked?
What is this? Is this real life?
Click to expand...
Click to collapse
NAND is NOT locked if you are in recovery mode.
But unfortunately the stock recovery mode doesn't allow adb, so it only works in rooted/modded ROMs.

Neotelos_com said:
NAND is NOT locked if you are in recovery mode.
But unfortunately the stock recovery mode doesn't allow adb, so it only works in rooted/modded ROMs.
Click to expand...
Click to collapse
maybe i'm wrong, but i thought that NAND was still locked. it's /system you can get to with our current root. if NAND was unlocked, then we could flash the eng build and get it stick. but, we can't.

hope this makes sense because these terms and concepts seem to be getting confused and rehashed in different threads. im all for brainstorming and being creative and hope i explain this well.
you're all correct, in all ROMs, EXCEPT toast's PC36IMG.zip (userdebug RUU), /system is NAND locked.
if you have root access in normal android mode (unrevoked, etc) and are able to make changes to /system, reboot and you'll see the changes don't stick cuz it is NAND locked.
if you're using toast's PC36IMG.zip (leaked userdebug RUU) recovery mode has root adb access AND NAND unlocked /system. hurray for a leak!
it is good to know the mount commands which we can use in the leaked userdebug RUU recovery mode because /system is NAND unlocked there.
but the mount commands won't help us in normal android mode UNTIL we can get past the NAND lock protection.

[Q] How to have write permission in some file in /system???

My captivate is already rooted, i use the Astro app to edit files and now im trying to edit the /system/etc/gps.conf, but when i try to save...does not save...i notice this file is read only rights. How can i edit that and save it???

to mount /system as read write, you need to be rooted (obviously) and open up an adb shell.
mount -o rw /dev/block/stl9 /system
depending on what kernel you're running and what filesystem /system is mounted as you *may* need to specify the filesystem ("-t vfat" for rfs, "-t ext4" for voodoo) but I've never had to before.

Mount system rw

Hi,
I mounted the system in rw mode via adb shell. Now, I want to reset it back to ro. Will it reset automatically after a reboot?

The-Droidster said:
Hi,
I mounted the system in rw mode via adb shell. Now, I want to reset it back to ro. Will it reset automatically after a reboot?
Click to expand...
Click to collapse
Yes, or you can 'adb shell mount -o ro,remount /system'

/system remounting as RO after explicit RW mount

I have used the adb shell to mount my system partition as RW (mount -o remount,rw /system) but it appears to revert to RO. I can't tell exactly why.
I wish to move app updates to /system.
I have used CF Auto Root to root the device.
I installed Titanium Backup Pro.
I have set the app mode to AUTO/indirect as recommended for Samsung devices.
I select Integrate updates to system ROM (or similar, I don't have the screen in front of me). As soon as I do this, the /system partition is remounted as read only (cat /proc/mounts | grep system)
TB just seems to hang. The Gmail base.apk has been copied to /system/apps and the com.google.android.gm-1 folder has been removed from /data/app.
If I don't mount /system as RW the same thing happens.
If I manually copy the app data from /data/app to /system/app and set the permissions the app still fails to function.
Does anyone have any ideas why this is happening?
EDIT:
I cannot load apks via adb - I am told I have a RO file system, even though I can clearly see the /system partition is mounted.