I wanted to start customizing a ROM for our s22 and I was wondering how can I make system and vendor partitions read-write
to edit the files inside
for ext4 it was possible to unshare_blocks. not sure it's possible for f2fs. but you could convert into ext4 still..
https://forum.xda-developers.com/t/...s-rw-in-super-partition.4120963/post-87115427
Related
Hey guys!
It has been already a while messing around with my Defy but one question still remains unanswered for me.
If /cache, /data and /system partitions are Ext3 formatted (you can check this by typing mount in Terminal Emulator), why do nandroid backup images have Yaffs2 filesystem then? Why does this conversion occur? Doesn't it make much more sense to image the partition in its original filesystem?
Thanks in advance...
Nandroid backup - image with YAFFS filesystem. - not dump of partitions.
When recovery is simply unpack files on the ext3 partition.
i suppose earlier (android) adoption of yaffs2 played a big part of that decision, but now it may very well be tar.
it's just a lot easier not to change what's not broken, isn't it?
Will soon be changed to TAR format (Recovery 4.0 will support the two formats)
It sounds good.
Wish the recovery would be more powerful after its source open.
Now, i know there are a *few* places in the dev section that have ext4 optimizations. But these "optimizations" are for the conversion from ext3 to ext4 without having the reformat and everything.
I've been trying (unsuccessfully) to change some of the ext4 mount flags for better speed. My problem is, everything i do in making a CWM flashable with a ext4 optimize sh script errors out with a Status 0. it doesn't even run.
But this time, i though i'd try a few things using adb shell. I got some tune2fs stuff working, so i thought i'd run an fsck on it. There isn't any fsck located on the phone. So i copied over a fsck.ext4, ran it but then got this error (and it also left my rom unuseable, but luckily i had a nandroid):
Code:
***file system was modified*** invalid argument passed to ext2 library while rewriting block inode bitmaps
.
And when doing an ls of /sbin, there isn't anything in there related to ext4, let alone ext3. So i'm wondering, why is our phone supports ext4 partitions, but doesn't actually have anything to support them?
EDIT: running just the tune2fs seems to have worked, just need to test out any differences found first.
[Q] Is Ext3 or Ext4 Partition for S3-Evolution-Beta3.1-Ultimate rom ?
Is Is Ext3 or Ext4 Partition for S3-Evolution-Beta3.1-Ultimate rom for galaxy ace s5830?
This is the post where they have mentioned it:
http://forum.xda-developers.com/show....php?t=1775257
Do we need Ext3 or Ext4 Partition for S3-Evolution-Beta3 ultimate only or we need it for S3-Evolution-Beta3.1 as well. Just to be sure in this case. Is it compulsory for S3-Evolution-Beta3.1 or we can do the normal wipe data and partition and install it from zip.
Can anyone provide me answer to this question?
Hey
Can someone tell me how do I modify update script to get f2fs on system partition? Thanks
any one?? I know there is line in script that formats /system/ to ext4 but I don't know how to delete it properly
I got it, if someone is interested here it is http://forum.xda-developers.com/showthread.php?t=2776430
Im sure most of us now know /data is formatted as F2FS
i am trying to format /data as EXT4 for testing purposes however i cant get it to boot
i have added a line in the fstab for ext4 on the /data partition
once i format /data as ext4 in twrp i get a error saying that the device is corrupt and that i need to format/wipe my device
anyone have any ideas on how i can get this working please
ok no longer get 'device is corrupt' message
just stuck on the google icon with the bar loading - still no boot.