Remount system writable

---

just do this and you can read and write the system partition

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.

Originally Posted by l33tlinuxh4x0r

just do this and you can read and write the system partition

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

Iv always seen it written like this

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

You can also do this:

mount /dev/block/mtdblock4 /system

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

Originally Posted by Jus10o

Iv always seen it written like this

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

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.

Originally Posted by Obama's>god

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

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.

Originally Posted by Neotelos_com

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.

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.