Database Users

Read-only file system

adb remount

Gregalous said:
adb remount
Click to expand...
Click to collapse
wow someone musta struck a nerve somehow lol

I see your adb remount and raise you the true command that runs
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

bow chicka bow wow

copy file to /system

how can i copy file to /system

remount the file system
ex.
mount -o rw,remount -t yaffs2 /dev/block/mtdblock5 /system

xcxda said:
remount the file system
ex.
mount -o rw,remount -t yaffs2 /dev/block/mtdblock5 /system
Click to expand...
Click to collapse
mount: Operation not permitted

tadasi said:
how can i copy file to /system
Click to expand...
Click to collapse
Read this, three different methods.
http://forum.xda-developers.com/showthread.php?p=7622713#post7622713

[Q] Writing to system?

I'v just rooted my Tab, I don't know if I'm losing the plot but I can't figure out how to write to the system partition? I can't find any apps that will work (for free) and "adb remount" doesn't work. "remount failed: Operation not permitted"
Am I missing something?

alias_neo said:
I'v just rooted my Tab, I don't know if I'm losing the plot but I can't figure out how to write to the system partition? I can't find any apps that will work (for free) and "adb remount" doesn't work. "remount failed: Operation not permitted"
Am I missing something?
Click to expand...
Click to collapse
adb remount doesn't work because /default.prop needs ro.secure set to 0 (not 1). This can't be changed easily without modifying the boot.img.
However, you can remount /system as a r/w filesystem using ADB by opening a shell and:
Code:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p1 /system
or
Code:
su
mount -o rw,remount -t ext3 /dev/mtdblock3 /system
Regards,
Dave

foxmeister said:
adb remount doesn't work because /default.prop needs ro.secure set to 0 (not 1). This can't be changed easily without modifying the boot.img.
However, you can remount /system as a r/w filesystem using ADB by opening a shell and:
Code:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p1 /system
or
Code:
su
mount -o rw,remount -t ext3 /dev/mtdblock3 /system
Regards,
Dave
Click to expand...
Click to collapse
Thanks, so which should I actually use, the former or the latter?

I've personally used the first command, but I saw the second one on another thread and it seems to work as well.
To be honest, I think it's ignoring the parameter anyway.
Regards,
Dave

[solved]adb remount

Hello,
Has anyone gotten adb remount to work? I always get
remount failed: operation not permitted
Click to expand...
Click to collapse
I've also tried
Code:
mount -o remount,rw /dev/block/mmcblk0p4 /system
both from adb and in the terminal emulator but I get the same response
Trying to push anything to /system just results in
failed to copy '<file>' to '/system/<path>': Read-only file system
Click to expand...
Click to collapse
Any ideas?

Root?
You are rooted right? and didn't forget to "su" before those shell commands? because the shell command works fine for me, I remount system and changed the fonts

apparently I was just making it more complicated than it needs to be. You don't need to specify the mount point. Just use
mount -o remount,rw /system

How do i set /system as RW forever ?

All partitions in Nook are RW, except /system, which is Read-only.
Is it possibly ?

gsms said:
All partitions in Nook are RW, except /system, which is Read-only.
Is it possibly ?
Click to expand...
Click to collapse
I think that's unwise for a number of reasons. In fact, I don't think it will let you do it. From what I remember that last time I forgot to change it back to RO after working on something I ended up in a boot loop.

nmyshkin said:
I think that's unwise for a number of reasons. In fact, I don't think it will let you do it.
...
Click to expand...
Click to collapse
It is indeed very unwise -- but nevertheless possible to have /system always mounted as rw by editing the boot-up initialization script file /init.rc and commenting out the second line of the two lines # 58-59:
Code:
mount ext2 /dev/block/mmcblk0p5 /system
# mount ext2 /dev/block/mmcblk0p5 /system ro remount

digixmax said:
It is indeed very unwise -- but nevertheless possible to have /system always mounted as rw by editing the boot-up initialization script file /init.rc and commenting out the second line of the two lines # 58-59:
Code:
mount ext2 /dev/block/mmcblk0p5 /system
# mount ext2 /dev/block/mmcblk0p5 /system ro remount
Click to expand...
Click to collapse
Please, could you tell me where to find the file "init.rc" ?
So in fact i only have to edit 1st row to 2nd row, right ?

gsms said:
Please, could you tell me where to find the file "init.rc" ?
Click to expand...
Click to collapse
The init.rc file is located at the root directory ("/").
So in fact i only have to edit 1st row to 2nd row, right ?
Click to expand...
Click to collapse
You'd need to comment out line #59
Code:
mount ext2 /dev/block/mmcblk0p5 /system ro remount
by inserting "#" at the beginning of that line
Code:
# mount ext2 /dev/block/mmcblk0p5 /system ro remount
to keep the device from remounting /system as ro.
Be warned: if you corrupt this init.rc file your NST will not boot or function properly.

It doesn't work at all.
I've changed that line, saved the file and restarted.
Afterthat the /system is read-only again and the file init.rc is the original one!

digixmax said:
The init.rc file is located at the root directory ("/").
Click to expand...
Click to collapse
Not really. The extracted copy of init.rc is in the root directory.
The actual init.rc is packed in the ramdisk.
Depending on which device you have, the ramdisk could be a file or packed in an image with the kernel.

Renate NST said:
Not really. The extracted copy of init.rc is in the root directory.
The actual init.rc is packed in the ramdisk.
Depending on which device you have, the ramdisk could be a file or packed in an image with the kernel.
Click to expand...
Click to collapse
How exactly to modify init.rc inside ramdisk, using bootutil.exe ?
Iam with (rooted) NST firmware 1.2.1