Question regarding /system being readonly...

[Guest PaulW21781]

I'm playing... bear with me...

/system is read only... Is this because of issues with bad blocks? (I seem to remember something being said about this...)

Reason being, I've been faffing in an adb shell...

# mount

rootfs / rootfs ro 0 0

tmpfs /dev tmpfs rw,mode=755 0 0

devpts /dev/pts devpts rw,mode=600 0 0

proc /proc proc rw 0 0

sysfs /sys sysfs rw 0 0

tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0

none /dev/cpuctl cgroup rw,cpu 0 0

/dev/block/mtdblock3 /system yaffs2 rw 0 0

/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0

/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0

tmpfs /app-cache tmpfs rw,size=8192k 0 0

/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0

/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_uti

e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

I got /system now to have rw instead of ro permissions... but is it safe??? Note...

/dev/block/mtdblock3 /system yaffs2 rw 0 0

Quick test...

# mkdir /system/newdir

mkdir failed for /system/newdir, Out of memory

Then reboots lol! So guess not!...

Edited May 1, 2010 by PaulW21781

[Guest Snarkasm]

I think Paul said it's ro because of special code protections HTC put in; they're disabled in recovery, but during normal use, you can mount /system, but if you try to actually do anything with it, the protection kicks in and reboots the phone, exactly what you saw.

[Guest PaulW21781]

Aye thats what I've been thinking... I've mounted it in recovery mode manually and played with it just fine there...

I'll have a go decompiling the boot.img file and playing with that, if its anywhere it has to be in there...