Yes, I have don't the searches, and tried a ton of stuff including formatting portions. Seems this is working on the international version, and most nexus devices. Is the a thread that might help, or has anyone heard success stories with our device.
I really hate starting new threads, but sgh-i747 seems not to have the information out there for ways to getbf2fs working for data, cache, AND system.
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Information on F2FS
There is some information in the Quantum thread starting with http://forum.xda-developers.com/showpost.php?p=53958476&postcount=17136 and several of the posts following it. I tried to get the ROM running but never could get the kernel to boot.
drbmm said:
There is some information in the Quantum thread starting with http://forum.xda-developers.com/showpost.php?p=53958476&postcount=17136 and several of the posts following it. I tried to get the ROM running but never could get the kernel to boot.
Click to expand...
Click to collapse
Same here.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Yes, I have don't the searches, and tried a ton of stuff including formatting portions. Seems this is working on the international version, and most nexus devices. Is the a thread that might help, or has anyone heard success stories with our device.
I really hate starting new threads, but sgh-i747 seems not to have the information out there for ways to getbf2fs working for data, cache, AND system.
Click to expand...
Click to collapse
Same question here, I can't even find the option to format data partition in f2fs. I installed latest version of TWRP (2.7.1.0) and I looked in Advanced wipes menu, I selected "Change filesystem" option and it showed me the filesystem choice menu, but I only get the option to use ext2, ext3, ext4 or fat, no f2fs option. I also tried with Philz recovery but I see no option for f2fs in it too.
Nico3d3 said:
Same question here, I can't even find the option to format data partition in f2fs. I installed latest version of TWRP (2.7.1.0) and I looked in Advanced wipes menu, I selected "Change filesystem" option and it showed me the filesystem choice menu, but I only get the option to use ext2, ext3, ext4 or fat, no f2fs option. I also tried with Philz recovery but I see no option for f2fs in it too.
Click to expand...
Click to collapse
philz has the option in mount advanced format and you have to toggle ext4-f2fs.
decronic has an successful method for the N5 and has been helpful in supplying tools to convert a rom f2fs and attempting to get me off the ground but the kernel seems to fail on my attempts.
here is a flashable zip to format system, data, and cache for the d2LTE devices. It will completely wipe the internals of the phone so be sure to have an external sd card prepared for your next steps.
"https://www.dropbox.com/s/4beylkg0gvhgitv/Format-All-Partitions-to-F2FS-d2lte.zip">https://www.dropbox.com/s/4beylkg0gvhgitv/Format-All-Partitions-to-F2FS-d2lte.zip
please keep me posted as I would really like to use the full potential of this device.
aircooledbusses said:
please keep me posted as I would really like to use the full potential of this device.
Click to expand...
Click to collapse
Will try when I come back from work. Supposedly CM11 is supported right out of the box, if you use newer than 06/30 version.
I'm attempting to make it work now. I installed Philz Recovery 6.48 instead of 6.26 and I now have the f2fs option. I tried formatting all partitions to f2fs (sytem, data and cache) and I modified the updater script, using the instructions in Quantum Kernel thread, but it failed to boot (won't go past boot splash screen). Now, I'll try to only format /data and /cache partitions.
Edit: using only f2fs on /data and /cache, it won't go past the boot animation. It's a pain in the ass for now, nothing's working.
Nico3d3 said:
I'm attempting to make it work now. I installed Philz Recovery 6.48 instead of 6.26 and I now have the f2fs option. I tried formatting all partitions to f2fs (sytem, data and cache) and I modified the updater script, using the instructions in Quantum Kernel thread, but it failed to boot (won't go past boot splash screen). Now, I'll try to only format /data and /cache partitions.
Edit: using only f2fs on /data and /cache, it won't go past the boot animation. It's a pain in the ass for now, nothing's working.[/QUOTE
try just data. cache always failed for me regardless of the kernel
Click to expand...
Click to collapse
It successfully booted by using f2fs only on /data but it stopped dead in its track, when it showed a screen telling me that encryption is unsucsessful and that I need to perform a factory reset. Looks like there's really no way at all to make it work. Flashing a different kernel didn't change anything.
Nico3d3 said:
It successfully booted by using f2fs only on /data but it stopped dead in its track, when it showed a screen telling me that encryption is unsucsessful and that I need to perform a factory reset. Looks like there's really no way at all to make it work. Flashing a different kernel didn't change anything.
Click to expand...
Click to collapse
No, there is a way. I'm not sure how to get system to stick. S3 mini has it, nexus devices, and others. it will happen soon I'm sure.
Sent from my Nexus 7 using XDA Premium 4 mobile app
thanks for ur efforts.
(trollin).
err on the side of kindness
http://review.cyanogenmod.org/#/c/68382/ maybe we'll be able to get it with what they added on the latest nightly
Quantum 5.2
Has anybody been able to get F2fs working on their s3? I have been experimenting for hours. So far ive gotten an infinite bootlogo formatting to f2fs and installing quantum 5.2. if i convert quantum 5.2 rom to f2fs and install it gets stuck on gimme pwncakes picture (kernel)
Edit: also getting the encryption error when formatting data only
f41lbl0g said:
Has anybody been able to get F2fs working on their s3? I have been experimenting for hours. So far ive gotten an infinite bootlogo formatting to f2fs and installing quantum 5.2. if i convert quantum 5.2 rom to f2fs and install it gets stuck on gimme pwncakes picture (kernel)
Edit: also getting the encryption error when formatting data only
Click to expand...
Click to collapse
Haven't managed to get it working yet.
I tried flashing a recent CM nightly (with the default kernel) in vanilla CWM, Philz Touch CWM, and TWRP and no luck with any of them. Flashing the Format-All-Partitions zip doesn't seem to work, and if I use the F2FS format options already included in Philz Touch, I am never able to mount /system afterwards. I didn't even have the option to switch to the new file system in TWRP.
So I'm not too sure what's going on. Is it a recovery issue? Or is our device somehow permanently limited to what file systems we can choose from? I'm out of ideas at this point.
f2fs s3
Theres barely any roms or kernels that support f2fs for the d2att s3. I think it has to do something with the compatibility of the rom. Pwncakes has said that his kernel does support f2fs, but im confused whether the rom supports f2fs. Also, most of the tools for f2fs are for the nexus devices, so there might be some error in the compatibility of them. Other devices like the i9300 have kernels that support f2fs as well as dualbooting, but it hasn't picked up for the d2att yet.
I'm not positive, but I think the kernel can be either-or, but the ROM can only be one or the other. So the ROM will have to be made specifically for f2fs.
compatibility
Major kernels such as Kt747, leankernel and QuantumKernel all support f2fs, but theres no compatible rom to go with it. I would love the speed boost of f2fs on my phone if it were possible.
The interesting thing is I tried the F2FS ROM converter tool that was posted in the Quantum thread. The output zip looked like it did in fact have some changes to reflect support for the file system, but I still couldn't get past the kernel image on boot with TWRP. With Philz Touch, I was still unable to mount /system after flashing the ROM.
Sent from my SAMSUNG-SGH-I747
I have a feeling that the slimkat rom will work with f2fs. Im going to try it out along with quantum kernel or kt747
f41lbl0g said:
I have a feeling that the slimkat rom will work with f2fs. Im going to try it out along with quantum kernel or kt747
Click to expand...
Click to collapse
please post back your progress. Device maintainer said that it has something to do with the Fstab that is preventing it from working for us.
my expirience with Dechronic's rom converter is that it makes use of a modified boot image. I fear the one I have is too old to working with so I am sort of stuck waiting for a further development. its a shame too, I have a spare S3 I can be a little risky with.
Related
Hello All,
I'm not expert in android platform. I found that there are many articles that are talking about F2FS performance in compare to EXT4.
Is there any tool to convert my device t889 to F2FS keeping the same experience? i.e. android 4.3, current ROM DN3 V3.2 LTE, and Kernel AGNI V3.9.4-OC-LTE
Regards
Guys ... Your reply please ... I think this may have significant performance change if it is doable ... Also if there is a way to override all system call to fsync() by fdatasysnc(), it will produce a massive performance change in the whole device
K3A said:
Guys ... Your reply please ... I think this may have significant performance change if it is doable ... Also if there is a way to override all system call to fsync() by fdatasysnc(), it will produce a massive performance change in the whole device
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2631278 try this rom
mattlowry said:
http://forum.xda-developers.com/showthread.php?t=2631278 try this rom
Click to expand...
Click to collapse
I just did the f2fs and had ROM running OK, did not see any improvement so I flashed CWM recovery and tried to restore a nandroid and it failed on data then phone would boot but gave me an error about having to reset phone. So i'm odining+root66ing my Note2 to get back to stock. I assume Im not f2fs any more.
Question? Once you switch to f2fs, do you have to use devil recovery from that point on to flash new roms?
Can some one explain the options to flashing a new roms once on f2fs, ex: what recovery can be used?
Converting to f2fs was not difficult and will do once again when I understand more.
Cheers, they really need a beer mug icon, but jolly face will do.
pvaldeben said:
I just did the f2fs and had ROM running OK, did not see any improvement so I flashed CWM recovery and tried to restore a nandroid and it failed on data then phone would boot but gave me an error about having to reset phone. So i'm odining+root66ing my Note2 to get back to stock. I assume Im not f2fs any more.
Question? Once you switch to f2fs, do you have to use devil recovery from that point on to flash new roms?
Can some one explain the options to flashing a new roms once on f2fs, ex: what recovery can be used?
Converting to f2fs was not difficult and will do once again when I understand more.
Cheers, they really need a beer mug icon, but jolly face will do.
Click to expand...
Click to collapse
Odin will format as ext4. You will need to keep devil recovery in order to keep f2fs as no other recovery can write to f2fs partitions. Ive found though that some zips dont like to install using devil recovery. Once partitions are f2fs, before you can do anything else with another recovery, you need to reformat the partitions back to ext4 ( or go through odin and start all over again lol ).
You will need to use devil and reformat the partitions back as ext4. Then flash cwm / phils touch recovery. Once thats done you can flash a new rom zip. To revert the new rom back to f2fs, Install a compatible kernel (agni and devil so far ), then flash devil f2fs recovery. Reboot to make sure things are working properly. Then reboot into devil recovery to do a nandroid, format f2fs, and restore the new nandroid.
Hope this helps! I just did a write up in the Jedi X2 thread with links.
Dont forget the thaks button
Sent from my SGH-T889 using xda app-developers app
pyraxiate said:
Odin will format as ext4. You will need to keep devil recovery in order to keep f2fs as no other recovery can write to f2fs partitions. Ive found though that some zips dont like to install using devil recovery. Once partitions are f2fs, before you can do anything else with another recovery, you need to reformat the partitions back to ext4 ( or go through odin and start all over again lol ).
You will need to use devil and reformat the partitions back as ext4. Then flash cwm / phils touch recovery. Once thats done you can flash a new rom zip. To revert the new rom back to f2fs, Install a compatible kernel (agni and devil so far ), then flash devil f2fs recovery. Reboot to make sure things are working properly. Then reboot into devil recovery to do a nandroid, format f2fs, and restore the new nandroid.
Hope this helps! I just did a write up in the Jedi X2 thread with links.
Dont forget the thaks button
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Yes Saw your post on JediX2 and used you link to get the devil recovery. really not difficult as you explained it. But just posted my question here as f2fs was deviating from rom thread. Thanks again. Cheers.
Read directions in op from thread provided by matt. Performance gains require a little more than converting file system. Added effort is well worth it.
Bruce lee roy said:
Read directions in op from thread provided by matt. Performance gains require a little more than converting file system. Added effort is well worth it.
Click to expand...
Click to collapse
Shore enough.
I readit and I'm going to try again.
Shore enough.
IF you are expert at ROMs and flashing you may find this helpful. I am really happy with the F2FS Filesystem on my OG Note; I've since bought the 2014 version, yet with F2FS the OG Note feels just as fast now. Samsung has put a lot of work into F2FS and reducing flash-based I/O waits is key for eliminating lag on Android.
I did the JB kernel first 'cause that's the source I had lying around. I'm going to build up a proper kernel source tree for KitKat for my 2014 Note in the next few days, then build one for the KitKat OG Note after that. The F2FS is from the tip of Linus' "master" branch, backported to the 3.0 kernel the OG Note uses.
I'm not going to do any newbie handholding- this is for experienced users- but the general way to use this is:
- Backup anything you'll want to save from your INTERNAL /sdcard, as it will be wiped
- Using an EXISTING TWRP (not the one here), make a backup of your /data (onto an external SD-Card)
- flash this recovery, then boot into it
- Wipe the /cache partition- it will reformat it as an F2FS partition
- "Advanced Wipe" the /data partition- use the "scary" wipe that says you'll lose EVERYTHING
- Do a /data (ONLY!) restore from the backup you'd just made from the previous (non-F2FS) recovery
- Wipe Dalvik Cache
- Shut down and go into Download (Odin) mode
- Flash the boot.img provided (it should work on any recent JB Samsung ROM)
- Reboot
- Restore any Internal /sdcard stuff you'd saved
- Enjoy speedy F2FS goodness (give it a minute after first-time booting so it can settle)
The boot.img is here.
The F2FS-enabled TWRP is here.
You know the rules- despite my testing and use, you may lose data, etc. etc. but if anyone uses this, be sure to let me know if it works for you, and especially if you have any issues with it. I'll put out the source to the kernel in time as well.
I've been thinking about going back to Jellybean, this might be the deciding factor.
Any chance on something for 4.4.4 aosp?
Airtioteclint said:
Any chance on something for 4.4.4 aosp?
Click to expand...
Click to collapse
This is fairly easy to add to any ROM where you've got all the source code (i.e., AOSP and its variants like CM, etc.). I'm pretty sure I won't be making one though, as most non-Samsung ROMs are usually lacking some functionality so I never use one.
Not working on 8013
I followed the instructions, but when I install the recovery, get a boot loop every time. But it was worth a try. Thanks for all your hard work.
:crying:
kcrudup said:
IF you are expert at ROMs and flashing you may find this helpful. I am really happy with the F2FS Filesystem on my OG Note; I've since bought the 2014 version, yet with F2FS the OG Note feels just as fast now. Samsung has put a lot of work into F2FS and reducing flash-based I/O waits is key for eliminating lag on Android.
I did the JB kernel first 'cause that's the source I had lying around. I'm going to build up a proper kernel source tree for KitKat for my 2014 Note in the next few days, then build one for the KitKat OG Note after that. The F2FS is from the tip of Linus' "master" branch, backported to the 3.0 kernel the OG Note uses.
I'm not going to do any newbie handholding- this is for experienced users- but the general way to use this is:
- Backup anything you'll want to save from your INTERNAL /sdcard, as it will be wiped
- Using an EXISTING TWRP (not the one here), make a backup of your /data (onto an external SD-Card)
- flash this recovery, then boot into it
- Wipe the /cache partition- it will reformat it as an F2FS partition
- "Advanced Wipe" the /data partition- use the "scary" wipe that says you'll lose EVERYTHING
- Do a /data (ONLY!) restore from the backup you'd just made from the previous (non-F2FS) recovery
- Wipe Dalvik Cache
- Shut down and go into Download (Odin) mode
- Flash the boot.img provided (it should work on any recent JB Samsung ROM)
- Reboot
- Restore any Internal /sdcard stuff you'd saved
- Enjoy speedy F2FS goodness (give it a minute after first-time booting so it can settle)
The boot.img is here.
The F2FS-enabled TWRP is here.
You know the rules- despite my testing and use, you may lose data, etc. etc. but if anyone uses this, be sure to let me know if it works for you, and especially if you have any issues with it. I'll put out the source to the kernel in time as well.
Click to expand...
Click to collapse
It's probably the overclocking. Let me make up a non-OC set soon.
I just got a Notification from the "PM Bot" about this- if anyone's (still interested in?) using this, let me know.
I'd love to use this if we could get F2FS with CM12! By i presume for jellybean only.
This is cool, as just about everyone else said would be great to see KK support for the GT-N8000 KK ROMs ported to GT-N8013. THANK YOU either way AWESOME WORK!
I thank @frantisek.nesveda for his Agnostic-kernel - partition independent kernel flasher on which I base this. I also thank everyone he thanks. Additionally, I thank anyone who posted about F2FS and formatting partitions. I read a lot of threads and I’m sure I gleaned something from everything I read.
For now this has to be done after flashing your preferred firmware (ROM). I recommend you make all your desired changes especially changing kernels.
Copy the files to your sdcard where you typically put flash files. I recommend an external card, because this is the only way I do it and I have not tested the other way. If you put it on your internal card it needs to be outside the /system and /data partitions because you'll lose them during formatting.
Also, I have only tested this on PhilZ Touch 6.58.9 recovery. I would appreciate anyone testing on other recoveries if you find one that supports f2fs.
If you are not on PhilZ 6.58.9, flash the zip and reboot to recovery.
Make a full back up of your ROM.
I also recommend you have an Odin based recovery plan. During my trials I ended up with a blank screen and used Odin to get back. This may not be the case with this latest PhilZ.
Format the partitions to f2fs.
It is in "Wipe and Format Options", then "Custom Format Options" then "Toggle f2fs <-> ext4 migration"
Remember, to format data you pick /sdcard. Also, this will remove everything on your internal card.
See warnings in post #2
I include a testF2FS zip to confirm the formatting.
Then use custom restore to get the data and/or the system from the backup. You can skip cache since it gets rebuilt.
Then flash GS3-F2FS-kernel-fstab-Fixer to adjust the kernel boot image to support the new formats.
This only fixes the fstab and if the kernel does not have f2fs support it will not work.
As always, no one is responsible for what happens to your phone. Everyone does this on their own and at their own risk.
Please do NOT mirror these files.
It appears to only work with the PhilZ recovery I built. If someone finds another please let us know.
Also, it does not work on TouchWiz ROMs. If someone finds one that it does work on please let us know.
Do not use the phone setting Factory Data Reset
XDA:DevDB Information
F2FS, Tool/Utility for the AT&T Samsung Galaxy S III
Contributors
RoryB
Version Information
Status: Beta
Beta Release Date: 2014-11-13
Created 2014-10-21
Last Updated 2014-12-06
Reserved
Latest files on Android File Host
Remember, to format data you pick /sdcard. Also, this will remove everything on your internal card.
Do not factory reset through the phone settings. This appears to format as ext4 and does not keep your formatting.
If you do you would need to try the f2fs fixer before rebooting. I have not so let us know how it goes if you try.
[OLD WAY]
For now this has to be done after flashing your preferred firmware (ROM).
Copy the files to your sdcard where you typically put flash files. I recommend an external card, because this is the only way I do it and I have not tested the other way. Also, I have only tested this on PhilZ Touch 6.48.4 recovery. I would appreciate anyone testing on other recoveries.
Make a full back up of your ROM.
It seems it is best to get everything the way you want before the back up, including any kernel changes.
I also recommend you have an Odin based recovery plan. During my trials I ended up with a blank screen and used Odin to get back.
Flash the zip file for what format you want to change. I include a testF2FS zip to confirm the formatting. For some reason it sometimes takes more than one try to format the partitions. Sometimes rebooting recovery helps before trying to confirm the formatting.
NOTE: Sometimes the phone reboots on its own while formatting. Be prepared to press the home and volume up buttons for two vibrations to get back to recovery. The first is the final power down and the second is the powering up. Remember to wait for the blue text in the upper left corner.
Then I use custom restore to get the data and/or the system from my backup. You can skip cache.
Then I flash GS3-F2FS-kernel-Fixer to adjust the boot image to support the new formats.
This only fixes the fstab and if the kernel does not have f2fs support it will not work. If they are getting upstream changes they should have it.
As always, no one is responsible for what happens to your phone. Everyone does this on their own and at their own risk.
Please do NOT mirror these files.
yahoo!!!! thank you for what had to have been alot of research , testing , and i cant imagine what-nots.:victory:
will try out tonite and report back
err on the side of kindness
Saving my response until after class... Thus is awesome
Sent from my HTC One_M8 using XDA Free mobile app
Look forward to testing tonight! Will post with results when I have them
Sent from my CARBON-SGH-I747
TheSchatz said:
Look forward to testing tonight! Will post with results when I have them
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
Two different phone both liquid ROM. F2fs all versus f2fs none
Thanks again Rory!!
Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747
TheSchatz said:
Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
I tried some stuff before with formatting partitions in twrp and it always failed. Even the newest 8.whatever just freaks out with unrecognized file system. I've not been a fan of philz ever before, but since that's what is working I Will adapt
aircooledbusses said:
I tried some stuff before with formatting partitions in twrp and it always failed. Even the newest 8.whatever just freaks out with unrecognized file system. I've not been a fan of philz ever before, but since that's what is working I Will adapt
Click to expand...
Click to collapse
I guess Philz it is, as latest CWM failed in the same fashion.
Yeah, same here with CWM.
Running vanilla CM11. Took a full nandroid, formatted system, cache, and data with Philz. Restored nandroid, installed latest Quantum kernel and flashed the kernel fix.
Everything is up & running, but performance has downgraded. AnTuTu score down by about 20%. I have seen other f2fs discussions that said it needs time to settle in, so I'll let the phone on all night and check it in the morning.
Just some more scores I am not too sure what to make of. But obviously f2fs has the edge.
Html5 test seems a bit fictitious but again shows f2fs showing some advantage....... If more birds is a good thing that is.
one more to confirm: failed with twrp 2.6.3.1 . tried multiple times. running Q v3.66 with appropriately dated kernels = QK / dkp / BMS .
ohh philzzz , where are you ? time to come and play.!
err on the side of kindness
mrrocketdog said:
one more to confirm: failed with twrp 2.6.3.1 . tried multiple times. running Q v3.66 with appropriately dated kernels = QK / dkp / BMS .
ohh philzzz , where are you ? time to come and play.!
err on the side of kindness
Click to expand...
Click to collapse
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/
I used one for d2lte. Please ignore the update to latest binary message
TheSchatz said:
Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
Remember, sometimes it takes a few times. I've been trying things like adding sleeps to "rest" between each format command. It did not help. I sometimes had to format, reboot to recovery, format again and then maybe it showed up as changed.
I think I got things mixed up. I have to set up boot image to support the new format and then flash quantumkernel. I"ll update the first post.
Yup, I use this one https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.zip
RoryB said:
Remember, sometimes it takes a few times. I've been trying things like adding sleeps to "rest" between each format command. It did not help. I sometimes had to format, reboot to recovery, format again and then maybe it showed up as changed.
I think I got things mixed up. I have to set up boot image to support the new format and then flask quantumkernel. I"ll update the first post.
Yup, I use this one https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.zip
Click to expand...
Click to collapse
Well, now I can't get past the kernel splash. Philz finally sees everything as f2fs, but I can't mount data at all... I've managed to royally screw up everything, lol. Off to Odin, I'll try again sometime but it's a no go for now.
Thanks for the files though, I'm really excited for the opportunity!
TheSchatz said:
Well, now I can't get past the kernel splash. Philz finally sees everything as f2fs, but I can't mount data at all... I've managed to royally screw up everything, lol. Off to Odin, I'll try again sometime but it's a no go for now.
Thanks for the files though, I'm really excited for the opportunity!
Click to expand...
Click to collapse
Yes, formatting is a bit wonky but the test zip file is very helpful. After formatting I'd run the test zip till desired partitions showed f2fs and not unknown. I also rebooted recovery before restoring. That custom restore really messed me up and I had to have only one back up to keep stuff straight. Then the fix file and a reboot. I only flashed qk 10.11 after it was all running.
Don't know if This will help anyone but it worked for me.
aircooledbusses said:
Yes, formatting is a bit wonky but the test zip file is very helpful. After formatting I'd run the test zip till desired partitions showed f2fs and not unknown. I also rebooted recovery before restoring. That custom restore really messed me up and I had to have only one back up to keep stuff straight. Then the fix file and a reboot. I only flashed qk 10.11 after it was all running.
Don't know if This will help anyone but it worked for me.
Click to expand...
Click to collapse
Eventually everything read f2fs, but I wasn't doing any data restoration. I was just going to start with a fresh rom install, but that's when I was stuck on the kernel splash with no adb. I'll probably try again tonight after work, maybe I'll have better luck!
Sent from my CARBON-SGH-I747
Many ROMs have format built into their updater script and that would undo your format to f2fs unless the ROM is written to support it.
Would it be possible to format the file system on this tablet for use with F2FS and how would I go by doing so if yes?
Grizzly6117 said:
Would it be possible to format the file system on this tablet for use with F2FS and how would I go by doing so if yes?
Click to expand...
Click to collapse
You'd need a custom Kernel.....I'm not aware of one that supports F2FS but can I ask a dumb question....why? There's still no Stable release out yet is there?
Yes. In addition to a F2FS enabled custom kernel, you would require an enabled custom recovery.
My SkyHigh kernel has in built F2FS support but never tested
UpInTheAir said:
Yes. In addition to a F2FS enabled custom kernel, you would require an enabled custom recovery.
My SkyHigh kernel has in built F2FS support but never tested
Click to expand...
Click to collapse
Yeah, I know by my post that I made my self to be clueless on things like this just wanted to see if people have already tested on this for this, I'm considering changing one of the ROMs to f2fs and test your kernel for f2fs compatibility, I'm just worried about bricking as I am on contract with this device but I don't see why I couldn't recover everything flashing stock with Samsung kies
F2FS
I managed to convert SuperSamsung v2 to F2FS by using a F2FS converter script I got from the Nexus 7 side of the forums and used your latest SkyHighKernel to boot into F2FS succesfully
EDIT: Feels snappier and less stutter, the major improvement atm is App Loading times
Grizzly6117 said:
I managed to convert SuperSamsung v2 to F2FS by using a F2FS converter script I got from the Nexus 7 side of the forums and used your latest SkyHighKernel to boot into F2FS succesfully
EDIT: Feels snappier and less stutter, the major improvement atm is App Loading times
Click to expand...
Click to collapse
Sweet. Can you please link to the script thread, and did you need to modify it for our device partition table?
UpInTheAir said:
Sweet. Can you please link to the script thread, and did you need to modify it for our device partition table?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2731666
Thats the Script I used, didnt change anything, but during the process when it asks what boot.img to use, you can select to use your own, and I simply just pulled it from your Kernel and placed into the folder directory, but I did flash the kernel zip anyway once flashing the ROM, I changed System and Cache to F2FS first, flashed ROM etc. then rebooted recovery and converted Data to F2FS, which wipes everything on internel Memory, so i kept my backup of everything on my External SD
Grizzly6117 said:
http://forum.xda-developers.com/showthread.php?t=2731666
Thats the Script I used, didnt change anything, but during the process when it asks what boot.img to use, you can select to use your own, and I simply just pulled it from your Kernel and placed into the folder directory, but I did flash the kernel zip anyway once flashing the ROM, I changed System and Cache to F2FS first, flashed ROM etc. then rebooted recovery and converted Data to F2FS, which wipes everything on internel Memory, so i kept my backup of everything on my External SD
Click to expand...
Click to collapse
Good stuff. Glad the kernel worked so far.
I clean flashed the Nougat beta 8 on FreedomOS CE 1.11 which is based on OOS beta 7) and I still have ext4 as my filesystem.
The thing works fine except I get serious lags during gaming. I am not sure if this is because of ext4 but I would love to try out F2FS.
Is there any way I can get to F2FS with minimal effort?
Or do I just have to clean flash 3.2.8, factory reset and then flash the beta?
I am basically looking for a better idea than above, if one exists.
Thanks!
mharis05 said:
l
The thing works fine except I get serious lags during gaming. I am not sure if this is because of ext4 but I would love to try out F2FS.
Click to expand...
Click to collapse
i am 100% sure that the lag you are facing is definitely not due to ext4.
If this game lags on ext4 then this game will also lag on f2fs
JumboMan said:
i am 100% sure that the lag you are facing is definitely not due to ext4.
If this game lags on ext4 then this game will also lag on f2fs
Click to expand...
Click to collapse
Acknowledged.
Can you advise if I still want to get F2Fs anyway?
mharis05 said:
Acknowledged.
Can you advise if I still want to get F2Fs anyway?
Click to expand...
Click to collapse
I will not advise converting partition to f2fs cause there will be no noticeable gain.
and converting partition to f2fs is lot of work. it requires backup of all stuff to pc , formatting whole partition.
And to use f2fs you have to flash custom kernel.
And even after doing this it will give Little to no benefit in real life usage.
===
in short if you are happy with current setup then keep as it is. but if you want to play with fire then go ahead.
mharis05 said:
Acknowledged.
Can you advise if I still want to get F2Fs anyway?
Click to expand...
Click to collapse
to get f2fs you'll have to wipe the partition you're converting,
get modified TWRP .28 , and in recovery go to advanced wipe, select data (or system) and then got to Repair or change File System.. in there select change file system, and there choose f2fs, after it's done go back to advanced wipe and wipe data ...repeat if you also want system (or internal storage) to be f2fs... DO It at you're OwnRisk
JumboMan said:
I will not advise converting partition to f2fs cause there will be no noticeable gain.
and converting partition to f2fs is lot of work. it requires backup of all stuff to pc , formatting whole partition.
And to use f2fs you have to flash custom kernel.
And even after doing this it will give Little to no benefit in real life usage.
===
in short if you are happy with current setup then keep as it is. but if you want to play with fire then go ahead.
Click to expand...
Click to collapse
Strange, I understand that a lot of people exaggerate when it comes to their phone's performance and battery, quite a few users reported noticeable difference after switching partitions.
Maybe because of the whole data wiping the phone got snappier and they mistook it for filesystem performance.
Also, I also read a few places that OOS 3.2.8 came with f2fs as default, i.e. if you factory reset, you can get f2fs with the stock kernel.
theduke7 said:
to get f2fs you'll have to wipe the partition you're converting,
get modified TWRP .28 , and in recovery go to advanced wipe, select data (or system) and then got to Repair or change File System.. in there select change file system, and there choose f2fs, after it's done go back to advanced wipe and wipe data ...repeat if you also want system (or internal storage) to be f2fs... DO It at you're OwnRisk
Click to expand...
Click to collapse
I already have TWRP .28 so that can be marked done.
I was reluctant on converting the partition using TWRP in the anticipation that it might give me a bootloop or something since I am on the Nougat beta which may not be too happy with TWRP filesystem conversion.
Can you tell if this should work on Nougat beta or you want me to try myself :silly:
mharis05 said:
Also, I also read a few places that OOS 3.2.8 came with f2fs as default, i.e. if you factory reset, you can get f2fs with the stock kernel.
Click to expand...
Click to collapse
No.
Stock kernel on oos 328 doesn't support f2fs. for f2fs you have to flash custom kernel like elementalx, blu_spark, etc.
JumboMan said:
No.
Stock kernel on oos 328 doesn't support f2fs. for f2fs you have to flash custom kernel like elementalx, blu_spark, etc.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...m-and-how-to-get-it-on-your-oneplus-3.474072/
See the forum above, F2FS is supported by the Community builds with stock kernel..
mharis05 said:
https://forums.oneplus.net/threads/...m-and-how-to-get-it-on-your-oneplus-3.474072/
See the forum above, F2FS is supported by the Community builds with stock kernel..
Click to expand...
Click to collapse
community builds are different from stock oos.
latest community builds support f2fs but not oos
Also, don't forget that stock OB8 only has support for F2FS on the /data partition, not the other partitions.
mharis05 said:
I already have TWRP .28 so that can be marked done.
I was reluctant on converting the partition using TWRP in the anticipation that it might give me a bootloop or something since I am on the Nougat beta which may not be too happy with TWRP filesystem conversion.
Can you tell if this should work on Nougat beta or you want me to try myself :silly:
Click to expand...
Click to collapse
yes it should work N Beta , but as mentioned above in another comment the N beta supports f2fs only on data so only convert the data partition...
you wont get bootloop as long as you stay on TWRP .28, i did get a bootloop when i flashed the official TWRP, actually i got a black screen then bootloop (was a bad situation)...so stay at ..28 as long as you're on Nougat and/or with the N beta firmware( because some CM roms require you to have the N beta firmware) other versions of TWRP are not compatible with N beta firmware
you'll get an extra messege about dm-verity ilike the one about the unlocked bootloader but that's normal.
if you want to go back you need to 1st convert the data back to ext4 , then flash the oos 3.2.6 (or above 3.2.7 or 3.2.8) firmware and modem (firmware only available on the forums) and then wipe everything then flash official TWRP then reboot back to recovery (official twrp) then follow the regular flashing procedures.(i prefer doing 1 more wipe on official TWRP), also after a full wipe that includes internal storage you need to reboot back to recovery (not system) then copy the required files back to internal storage and flash
mharis05 said:
I clean flashed the Nougat beta 8 on FreedomOS CE 1.11 which is based on OOS beta 7) and I still have ext4 as my filesystem.
The thing works fine except I get serious lags during gaming. I am not sure if this is because of ext4 but I would love to try out F2FS.
Is there any way I can get to F2FS with minimal effort?
Or do I just have to clean flash 3.2.8, factory reset and then flash the beta?
I am basically looking for a better idea than above, if one exists.
Thanks!
Click to expand...
Click to collapse
you should wait for the official 7.0 from oneplus. like I am. if you gain f2fs system, there won't be any performance improvement or whatsoever.
Backup your data and do factory reset you'll get f2fs. In my experience my OP3 feels snappier. Cold start of apps are improved.
Wiped the /data partition using TWRP (28) without selecting System or internal storage.
Now /data partition is f2fs - which is the intended partition as per OnePlus.
Thread can be closed.