Good morning, I was wondering if I start resizing my 6T's partitions with TWRP, will it break safetynet? I know that generally modifying the filesystem or the files on the /system partition will break it, but wanted to know if resizing the partition as a whole would as well. I'm currently on the latest OxygenOS. Thanks!
Related
Hi,I installed topogigi's rom because it had webtop and everything seemed fine,and THEN I read this
"
you can simply use ext4 conversion directly from recovery(THE CWM ONE!) just go in advanced and upgrade to ext4 system;data;cache...
DON'T UPGRADE OSH TO EXT4(WEBTOP PARTITION) CAUSE IT WILL CAUSE THE OSH NOT TO BE MOUNTED (AKA DELETED!)...
I THINK THERE IS A BUG IN RECOVERY EXT4 SCRIPT CAUSE OSH SHOULD WORK EVEN WHEN EXT4"
But...of course I had already converted the file system even the osh...
What to do now people?
I don't have a clue,do I need to reflash something ,to convert the ext4 osh into something else? How?
I'm pretty lost ....
Sent from my ATRIX
Easiest is to reinstall the osh partition (I assume you likely have no files you really care about on it).
Find a webtop.zip for the ATT rom that top's stuff is based on (I assume it is a 2.3.6).
http://forum.xda-developers.com/showthread.php?t=1163009
Once you have that on your phone, just go to recovery and reformat the OSH partition (to put it back as EXT3) and install the zip.
If you really want to keep the webtop you have, it can be done but it more difficult and likely not worth the effort .
EDIT: If you are not certain if it is broken, take a look to see /osh has anything in it. If it is empty, it is broken (not being mounted). If you see a standard looking unix tree, it is fine. It actually can be mounted as an EXT4, but that would take some playing around with system files (see how "webtop to sdcard" gets around the mount problem).
I recently switched from ext4 to f2fs file system on all partitions. After that I flashed omni's nightly in order to update and noticed that my /system partition was reverted to ext4 due to the reformat while flashing.
I think it would be helpful if the OmniROM zips contained some sort of check routine, so the file system type could be preserved and future updates are possible without the whole process of backing up, reformatting and restoring again.
I know the file system type depends on kernel support and also the custom recovery must be able to work with it, but I think it's the users responsibility anyway. I mean, either you know what you're doing or you leave it alone, right?
I hope this gets realised or there is some compromise. Currently I'm using latest OmniROM with Devil's recovery and kernel without dualboot.
Sent from my GT-N7100 using Tapatalk
klenamenis said:
I recently switched from ext4 to f2fs file system on all partitions. After that I flashed omni's nightly in order to update and noticed that my /system partition was reverted to ext4 due to the reformat while flashing.
I think it would be helpful if the OmniROM zips contained some sort of check routine, so the file system type could be preserved and future updates are possible without the whole process of backing up, reformatting and restoring again.
I know the file system type depends on kernel support and also the custom recovery must be able to work with it, but I think it's the users responsibility anyway. I mean, either you know what you're doing or you leave it alone, right?
I hope this gets realised or there is some compromise. Currently I'm using latest OmniROM with Devil's recovery and kernel without dualboot.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
That's a lot of work and means maintainers then have to officially support testing two different filesystem configurations.
f2fs on /system is pointless since /system is only written to when updating. Even Motorola, one of the first OEMs to actually use f2fs, only uses it for /data
For devices that don't already use it, I'm not transitioning them. It doesn't offer enough performance benefits to compensate for its piss-poor data integrity. A filesystem that can get corrupted to the point of needing a complete format just to get its fsck to run without crashing (this has already happened to me TWICE on the Moto G) is just not ready for production.
Entropy512 said:
f2fs on /system is pointless since /system is only written to when updating. Even Motorola, one of the first OEMs to actually use f2fs, only uses it for /data
For devices that don't already use it, I'm not transitioning them. It doesn't offer enough performance benefits to compensate for its piss-poor data integrity. A filesystem that can get corrupted to the point of needing a complete format just to get its fsck to run without crashing (this has already happened to me TWICE on the Moto G) is just not ready for production.
Click to expand...
Click to collapse
Well, pretty much makes sense. I just updated and let system be ext4 formatted from now on.
Sent from my GT-N7100 using Tapatalk
My Idea is to change the Filesystem on my d802.
Via adb I pulled the whole /data/media partion so that I can Push it back later.
I am not really Sure how this will work with the System partition.
I believe that flashing a cloudy G3 rom will Format the System partition back to ext4 (i think it's in the install Script).
So Would it be possible that I remove that "formating System" line to keep f2fs. Any other thoughts on this?
I was wondering that with TWRP 3.0, it is possible to convert the file system to f2fs. The performance in f2fs seems to be far greater when compared to ext4. Has anyone tried converting the x play to f2fs? If so, what all ROMs are compatible with it?
varounmirchi said:
I was wondering that with TWRP 3.0, it is possible to convert the file system to f2fs. The performance in f2fs seems to be far greater when compared to ext4. Has anyone tried converting the x play to f2fs? If so, what all ROMs are compatible with it?
Click to expand...
Click to collapse
I don't think it's possible to convert a filesystem to another, you'll probably need to format your partition in f2fs, so make a backup first.
Also, note that f2fs is designed to take advantage of nand-based storage. Have a look at http://www.xda-developers.com/f2fs-put-to-the-test-against-ext4/
claudineimatos said:
I don't think it's possible to convert a filesystem to another, you'll probably need to format your partition in f2fs, so make a backup first.
Also, note that f2fs is designed to take advantage of nand-based storage. Have a look at http://www.xda-developers.com/f2fs-put-to-the-test-against-ext4/
Click to expand...
Click to collapse
As far as I know, you do need to format in order to convert. I don't think any kind of conversion tool exists at this point, or may ever exist. I remember reading that there's only really a benefit to making the data partition f2fs (and perhaps the cache as well? I'm pretty tired atm so I can't confirm that.) If so, you should be able to format Data without reinstalling the ROM. Correct me if I'm mistaken!
Be aware that while f2fs is definitely faster, filesystems are relatively simple things that wind themselves into complex knots when put into action. So, despite f2fs being optimized for NAND, it hasn't been thoroughly tested the way EXT4 and others have. You could always run into some issues with data loss or other confusing bugs. Because of this, it's probably also safer to leave the System partition as EXT4, if you even can/would want to make it f2fs.
I'd also like to know if anyone has gotten f2fs working on the Moto X Play, @squid2 has f2fs driver updates listed in the changelog for his kernel, although it may also take support in the ROM to fully implement. Please let us know if you get it running! The performance is significantly faster, and it's also less wear-and-tear on the memory, if I understand correctly.
JohnHorus said:
As far as I know, you do need to format in order to convert. I don't think any kind of conversion tool exists at this point, or may ever exist. I remember reading that there's only really a benefit to making the data partition f2fs (and perhaps the cache as well? I'm pretty tired atm so I can't confirm that.) If so, you should be able to format Data without reinstalling the ROM. Correct me if I'm mistaken!
Be aware that while f2fs is definitely faster, filesystems are relatively simple things that wind themselves into complex knots when put into action. So, despite f2fs being optimized for NAND, it hasn't been thoroughly tested the way EXT4 and others have. You could always run into some issues with data loss or other confusing bugs. Because of this, it's probably also safer to leave the System partition as EXT4, if you even can/would want to make it f2fs.
I'd also like to know if anyone has gotten f2fs working on the Moto X Play, @squid2 has f2fs driver updates listed in the changelog for his kernel, although it may also take support in the ROM to fully implement. Please let us know if you get it running! The performance is significantly faster, and it's also less wear-and-tear on the memory, if I understand correctly.
Click to expand...
Click to collapse
Actually TWRP allows to convert the file system to f2fs (yes by formatting it obviously). Its usually recommended to convert the /data and the /cache partitions for optimum results. I had a Yu Yuphoria before this, and I had converted the file system to f2fs, and the performance was whooping fast.
And I did see that @squid2 has mentioned f2fs support in his kernel (i guess it comes directly from CAF) but I wanted to know which ROMs do support it? So far I don't see "f2fs supported" mentioned in any of the ROMs for our device and thats why I am still on hold.
We're already using f2fs. Even the stock ROM uses f2fs for the userdata partition.
So can we use f2fs with your Kernel and CM13? Data and cache partitions?
squid2 said:
We're already using f2fs. Even the stock ROM uses f2fs for the userdata partition.
Click to expand...
Click to collapse
Cache shows up as ext4 in TWRP, for me at least. Would that benefit from switching to f2fs?
Edit: Tried formatting the cache as f2fs, no boots.
F2fs does use a log, but still, it took up 128MB of the cache partition, seems kinda weird unless the partition actually grows to accomodate that. Maybe I did something wrong, idk.
Previously on Oxygen OS 4.5.15 running your /data partition on F2FS had no problems.
However currently if you try running your /data partition with F2FS either you get an infinite boot loop or if you're decrypted you get an error message that says "Encryption unsuccessful" I'm assuming that's just the kernel being unable to mount the /data partition and just assuming it was a bad encryption or corrupted partition message.
Default partition layout for /data seems to be EXT4 and that works correctly just posting a new topic here to see if anyone else knows the status of F2FS was it removed form OxygenOS 5 kernel?
vortex-5 said:
Previously on Oxygen OS 4.5.15 running your /data partition on F2FS had no problems.
However currently if you try running your /data partition with F2FS either you get an infinite boot loop or if you're decrypted you get an error message that says "Encryption unsuccessful" I'm assuming that's just the kernel being unable to mount the /data partition and just assuming it was a bad encryption or corrupted partition message.
Default partition layout for /data seems to be EXT4 and that works correctly just posting a new topic here to see if anyone else knows the status of F2FS was it removed form OxygenOS 5 kernel?
Click to expand...
Click to collapse
By default, OxygenOS (OOS) comes with File Based Encryption (FBE) enabled. FBE, at present, is not compatible with F2FS and hence OnePlus has the /data partition defaulting to EXT4.
If you wish to use F2FS on /data, you'd need to be decrypted, a. and b. you'd need a kernel that supports booting with F2FS as well. Also, I'm not sure but I think the latest TWRPs for OP5 also don't have the necessary stuff to convert the filesystem to F2FS, but I haven't checked that myself, so can't say that with certainty.