The Nexus 7, Nexus 5, Moto G, and Moto X all have f2fs support in some kind. It has made a fast improvement on my N7. Was wondering if any devs want to form a team to build up f2fs support for our device.
Would be willing to help.
Sent from my KFTHWI using xda app-developers app
Dude, come into #lg-g2 and ask. Hours of activity are pretty similar to how #lg-optimus-g were back this time last year.
Sent from my LG Optimus G using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2764480
Looks like they got F2FS working on the E975. No idea if its possible to take this and monkeywrench it for the E970, but its nice progress!
I hope the F2FS interest for this device doesn't die here. I've tested it out on the Nexus 7 and it basically made the device a whole new, usable experience. I would love to see the benefits that our aging geebs can get from it to extend their lifespan and usability.
nygfan760 said:
The Nexus 7, Nexus 5, Moto G, and Moto X all have f2fs support in some kind. It has made a fast improvement on my N7. Was wondering if any devs want to form a team to build up f2fs support for our device.
Click to expand...
Click to collapse
My TWRP build and AK kernel both support it. I've tried it and I think it worked.
Sent from my LG Optimus G using Tapatalk
brothaedhung said:
My TWRP build and AK kernel both support it. I've tried it and I think it worked.
Sent from my LG Optimus G using Tapatalk
Click to expand...
Click to collapse
I had no idea. That's awesome! I checked the TWRP and, sure enough, it can format f2fs. Any chance you can build a version of your PAC rom that does f2fs-all (except, of course, external sd)? I'd be happy to test it!
Level99 said:
I had no idea. That's awesome! I checked the TWRP and, sure enough, it can format f2fs. Any chance you can build a version of your PAC rom that does f2fs-all (except, of course, external sd)? I'd be happy to test it!
Click to expand...
Click to collapse
For the ROM, I think you just have to edit the updater-script to format system as F2FS instead of ext4. Haven't tried it yet, but I will tonight if I have time.
There's playstore apps that will do it too.
I've successfully formatted system F2FS, but haven't tried data yet since I think you lose everything when you format?
brothaedhung said:
For the ROM, I think you just have to edit the updater-script to format system as F2FS instead of ext4. Haven't tried it yet, but I will tonight if I have time.
There's playstore apps that will do it too.
I've successfully formatted system F2FS, but haven't tried data yet since I think you lose everything when you format?
Click to expand...
Click to collapse
Yeah, it does. I tried your rom with system as ext4 and data as f2fs and it popped up with the encrypted storage dialog and there was no way to get around it. I figure the kernel may only support f2fs for system right now.
I'll try manually changing the updater script for f2fs for system. I got one of the apps for f2fs conversion but it only currently supports nexus 4, 5, and 7. I emailed to request support be added for e970.
Sent from my LG Optimus G using XDA Premium 4 mobile app
Level99 said:
Yeah, it does. I tried your rom with system as ext4 and data as f2fs and it popped up with the encrypted storage dialog and there was no way to get around it. I figure the kernel may only support f2fs for system right now.
I'll try manually changing the updater script for f2fs for system. I got one of the apps for f2fs conversion but it only currently supports nexus 4, 5, and 7. I emailed to request support be added for e970.
Sent from my LG Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
also let me try making an updated TWRP build. I read somewhere about issues with data f2fs on early 2.7.1 builds.
brothaedhung said:
also let me try making an updated TWRP build. I read somewhere about issues with data f2fs on early 2.7.1 builds.
Click to expand...
Click to collapse
Alright, thanks. I tried changing the ext4 to f2fs and it failed to flash. Will keep tinkering but I did see another method that involved backing up the system, data, and cache partitions, and then restoring while enabling a TWRP option forcing the restores to restore as f2fs. Don't know if that's also something that can be added when you make the new TWRP build.
Level99 said:
Alright, thanks. I tried changing the ext4 to f2fs and it failed to flash. Will keep tinkering but I did see another method that involved backing up the system, data, and cache partitions, and then restoring while enabling a TWRP option forcing the restores to restore as f2fs. Don't know if that's also something that can be added when you make the new TWRP build.
Click to expand...
Click to collapse
Did you ever attempt this? Is there some roadblock that prevents our geeb from utilizing F2FS? I feel as though the interest in F2FS died down almost immediately lol
topdawg7793 said:
Did you ever attempt this? Is there some roadblock that prevents our geeb from utilizing F2FS? I feel as though the interest in F2FS died down almost immediately lol
Click to expand...
Click to collapse
The latest TWRP I had access to on the geeb did not have an option to force restore to F2FS. We'd need an update to the recovery that adds it, and even then, not sure it will work.
My main these days is a Moto G 4G LTE and, considering the specs, it should not be as snappy and responsive as it is. F2FS really does seem to add new life to middling device hardware, so I can't imagine what it would do to the geeb with its previous flagship specs.
Level99 said:
The latest TWRP I had access to on the geeb did not have an option to force restore to F2FS. We'd need an update to the recovery that adds it, and even then, not sure it will work.
My main these days is a Moto G 4G LTE and, considering the specs, it should not be as snappy and responsive as it is. F2FS really does seem to add new life to middling device hardware, so I can't imagine what it would do to the geeb with its previous flagship specs.
Click to expand...
Click to collapse
Ah, I see. The ramdisk needs to know what partitions are f2fs too right? All that stuff goes above what I'm capable of lol
topdawg7793 said:
Ah, I see. The ramdisk needs to know what partitions are f2fs too right? All that stuff goes above what I'm capable of lol
Click to expand...
Click to collapse
I built a ROM with a modified ramdisk and updater script. It flashes but doesn't get past the boot animation.
brothaedhung said:
I built a ROM with a modified ramdisk and updater script. It flashes but doesn't get past the boot animation.
Click to expand...
Click to collapse
Hmm..The only thing I can think of that could cause that is maybe the ROM didn't compile properly.
The key is to flash the rom, and kernel, and whatever, then afterwards format /data and /cache as f2fs using TWRP.
@brothaedhung do you have an F2FS kernel I can test?
nygfan760 said:
The key is to flash the rom, and kernel, and whatever, then afterwards format /data and /cache as f2fs using TWRP.
@brothaedhung do you have an F2FS kernel I can test?
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/61238/
brothaedhung said:
I built a ROM with a modified ramdisk and updater script. It flashes but doesn't get past the boot animation.
Click to expand...
Click to collapse
Have you tried this with the new TWRP?
topdawg7793 said:
Have you tried this with the new TWRP?
Click to expand...
Click to collapse
Not the one I built a couple of days ago, but I did with the fixed 2.7.1 that correctly formatted f2fs.
brothaedhung said:
Not the one I built a couple of days ago, but I did with the fixed 2.7.1 that correctly formatted f2fs.
Click to expand...
Click to collapse
Hmm okay. We'll only see a noticeable performance gain if the system partition is f2fs right? I doubt we'll gain much with just the data and cache being f2fs.
Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the Nexus One. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. I've only tested it quickly on my Nexus One, and it seems to work.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-passion.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-passion.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Thanks for compiling and posting this update here. I hope it works better than 3.0.0.5
If you're testing it, let me know if it works.
Sent from my Nexus S using Tapatalk
did anyone test this, does it resolve the damaged sd-ext partition in 3.0.0.5 one ??
gwassef said:
did anyone test this, does it resolve the damaged sd-ext partition in 3.0.0.5 one ??
Click to expand...
Click to collapse
Not using sd-ext on my N1, so I don't know. But 3.0.0.5 never damaged it back when I was using sd-ext.
Sent from my Nexus S using Tapatalk
I got it damaged 2 times, I thought it was my S2E app, but when i sent them they told me remove the 3.0.0.5 as it is known with this issue, install an older version. Since i installed the release before this one, i have no problems at all.
zyonee said:
Not using sd-ext on my N1, so I don't know. But 3.0.0.5 never damaged it back when I was using sd-ext.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
zyonee said:
If you're testing it, let me know if it works.
Click to expand...
Click to collapse
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Kelvino9 said:
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Click to expand...
Click to collapse
Should work, but you'll need to try it.
For some reason, ROM manager doesn't work for me. It downloads the rom, asks me if i want gapps, wipe /etc, then it reboots but NOT in recovery, and if i select Recovery, doesn't work. (goes back to original screen)... any ideas..?
joesatri said:
For some reason, ROM manager doesn't work for me. It downloads the rom, asks me if i want gapps, wipe /etc, then it reboots but NOT in recovery, and if i select Recovery, doesn't work. (goes back to original screen)... any ideas..?
Click to expand...
Click to collapse
Is the recovery properly flashed? Works well on my NS
Sent from my Nexus S using Tapatalk
sorry, blonde moment :L
Installed this recovery in my N1, works great. Maybe stupid question...Is there any way to make recoverys font bigger....There is so many space, but the font is so small...
Spakainz said:
Installed this recovery in my N1, works great. Maybe stupid question...Is there any way to make recoverys font bigger....There is so many space, but the font is so small...
Click to expand...
Click to collapse
You'll have to ask koush or the other devs about that. I only compiled from source. I'm not that skilled at modding this kind of code...
Sent from my Nexus S using Tapatalk
This recovery works well for me. Flashed using fastboot.
I also used this recovery to reformat the sd-ext partition and now my nandroid backups complete without freezing (they would freeze on the sd-ext backups last time requiring a battery pull).
Thanks for compiling and sharing this!
-D
Kelvino9 said:
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Click to expand...
Click to collapse
restoring doesn't work with sd-ext (1GB ext4 in my case): it's always aborting during restoring data! no cache and sd-ext restoring and no "restore completed" CWM message but jumping back to the CWM main menu.
it's the same with the other CWM3.2.0.1 for Nexus One.
:-(
This Corrupts EXT partition!
This recovery corrupts EXT partition while the 2.4.0.1 doesn't restore!!! I'm staying away from clockwork recoveries from now on! I'm sick and tried of restoring corrupt ext partitions!
sir*mez said:
This recovery corrupts EXT partition while the 2.4.0.1 doesn't restore!!! I'm staying away from clockwork recoveries from now on! I'm sick and tried of restoring corrupt ext partitions!
Click to expand...
Click to collapse
So it's safe if not using sd-ext. Sorry I can't help solve the problems...
Sent from my Nexus S using Tapatalk
accuphase said:
restoring doesn't work with sd-ext (1GB ext4 in my case): it's always aborting during restoring data! no cache and sd-ext restoring and no "restore completed" CWM message but jumping back to the CWM main menu.
it's the same with the other CWM3.2.0.1 for Nexus One.
:-(
Click to expand...
Click to collapse
Yes, now having the same problem with sd-ext backups too.
zyonee said:
Only available in standard orange, I actually can't be bothered to find out how to make different color variants.
Click to expand...
Click to collapse
Aww
But still, thanks for bringing it over to the N1.
Updated OP to version 4.0.0.0.
I wanted to post this here since I've been busting my tail on an update for a week now. This WILL flash, Backup & Restore android 4.4 roms! USB mounting, internal & external sdcard mounts as well. There are still a few bugs to work out but give it a go & some feedback. It's still a WIP but plenty stable to use daily for now.
Also anyone interested in flashing the CandyKat sweetener packs, you may now do so with this recovery!!
TWRP 2.8.7.0
I am not responsible for misuse, bricks, or exploding devices! Flash at your own risk! You can download the zip file & flash it from within your existing recovery & reboot to recovery.
CREDITS: Javelinanddart for fixing mounts, f2fs, & for fixing vibration for 5.0 & up Disconnecktie && Santod040 I have bugged these guys to death to get this working so Please stop in & thank these guys as well. They are a huge part of the success of this! Obviously this couldn't happen without Omniroms Source! And a huge thanks for
Dees_Troy for his guide to compiling twrp recovery!!
TWRP Themes have changed a bit & if you use a them then you'll want to checkout this link.
THEMING TWRP THE NEW WAY!
What's new in 2.8.7.0
- Initial ground work for software drawn keyboard (_that)
- Fix handling of wiping internal storage on datamedia devices (xuefer)
- Allow DataManager to set and read values from the system properties (xuefer)
- Fix crash when taking screenshots on arm64 devices (xuefer)
- Fix error message after an ORS script completes (Dees_Troy)
- Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
- Add system read only option - more details below (Dees_Troy)
- Add resize2fs and GUI option to run resize2fs (Dees_Troy)
- Fix crash loop caused by empty lines in AOSP recovery command file (_that)
- Prevent duplicate page overlays such as multiple lock screens (mdmower)
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don't take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
THEMING?
USE 1080P THEMES
Yeah!!
This is working perfect! Damn I missed TWRP. So freaking sweet!!
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Works well except mount memory
Liwais said:
Works well except mount memory
Click to expand...
Click to collapse
Mounting which partition? Anyone that finds an error or a bug should try posting the recovery log after said error. Don't post the entire log in a post but put it on pastebin or something similar. Having the logs greatly increases the likely hood the issue will be fixed. Thanks.
Liwais said:
Works well except mount memory
Click to expand...
Click to collapse
What do you mean by mount memory? Where you add something from the pc to the sd card & it shows up on the internal when in twrp? The internal sd card mounts when connected to the pc, not the external sd. I don't know if that's how it's suppose to work or not. This is my first twrp attempt and I had to build it from scratch basically. Like Disconnecktie stated, a log may be helpful.
Great work. Missed TWRP. Just had to tick off my internal sd. Panicked when my partition wasn't visible with my ROMs to flash. LOL.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I had in mind when're in rekaveri not mount the memory to your PC
Maybe this Problem just me, let me know
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
gimmeitorilltell said:
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
Click to expand...
Click to collapse
For some reason (most likely that I'm a dummy, or missed reading somewhere)
Recently my SD card took a poo, so I've been saving to internal memory.
I flashed TWRP. When I look in sdcard I have no files visible. When I am booted into CandyKat I can see my files with my file explorer. Am I missing a valid mount somewhere? When I go to / I don't see a folder called storage, and in my /sdcard all I see is a folder called TWRP which is empty.
THanks!
skearton said:
For some reason (most likely that I'm a dummy, or missed reading somewhere)
Recently my SD card took a poo, so I've been saving to internal memory.
I flashed TWRP. When I look in sdcard I have no files visible. When I am booted into CandyKat I can see my files with my file explorer. Am I missing a valid mount somewhere? When I go to / I don't see a folder called storage, and in my /sdcard all I see is a folder called TWRP which is empty.
THanks!
Click to expand...
Click to collapse
When you are in TWRP recovery are you selecting "Internal SDcard" or "MicroSD card"
Edit: Latest twrp recovery with vibrations enabled!
gimmeitorilltell said:
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
Click to expand...
Click to collapse
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
No it was not. I've been waiting on more feedback from the update or any of my twrp builds. Now that I'm aware of it, I'll look into that so we can get it official in Bigbiffs twrp thread. I think it's close enough for him to release it as an official but this is my personal feelings. It'll be a couple days maybe before I get back to it since I've spent the last week concentrating on this, it's time for me to move on to other things for a moment.
Sent from my HTC One Max using Tapatalk!
Newest build is working g sweet gimme. Love how ya added the button vibrate too. So far I've done 3 full wipes/flashes and your twrp has been flawless thanks for bringing this to us gimme.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
developweb said:
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
We can probably keep this here until the bugs are worked out. Have you tried the latest here yet? I don't theme my recovery but I'm willing to so I can get it correct.
Also that may be something you can set in twrp, set a different default path for themes but I'm not 100% sure.
gimmeitorilltell said:
We can probably keep this here until the bugs are worked out. Have you tried the latest here yet? I don't theme my recovery but I'm willing to so I can get it correct.
Also that may be something you can set in twrp, set a different default path for themes but I'm not 100% sure.
Click to expand...
Click to collapse
Default path in latest is correct now. Themes work from the correct directory now (/sdcard/TWRP/theme/ui.zip ) so they won't get deleted. Love button vibration as well! Excellent work.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
Default path in latest is correct now. Themes work from the correct directory now (/sdcard/TWRP/theme/ui.zip ) so they won't get deleted. Love button vibration as well! Excellent work.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Thank you for the feedback, it is very much appreciated! If you run into anything else, good or bad, Please feel free to give a shout out. I have OCD and with the vibration as an option, well it just was NOT an option to NOT work.. Lol
gimmeitorilltell said:
Thank you for the feedback, it is very much appreciated! If you run into anything else, good or bad, Please feel free to give a shout out. I have OCD and with the vibration as an option, well it just was NOT an option to NOT work.. Lol
Click to expand...
Click to collapse
I tried to install the full aroma rom patch by pollution and it seemed to work but gave com.android.phone error on boot. So I thought easy fix, I'll restore the backup I made with TWRP yesterday and got even more errors. Yes, I factory reset before restoring. It seems that this TWRP is not doing everything like it used to under the 4.2's. I'm going to go back to CWM and restore a CWM backup, regroup, recharge.......and try again from scratch to test this thing out again. Wish me luck.
Liwais said:
I had in mind when're in rekaveri not mount the memory to your PC
Maybe this Problem just me, let me know
Click to expand...
Click to collapse
I'm not sure that I understand what you're saying? The internal sd mounts to the pc once you go into twrp & mount it.
developweb said:
I tried to install the full aroma rom patch by pollution and it seemed to work but gave com.android.phone error on boot. So I thought easy fix, I'll restore the backup I made with TWRP yesterday and got even more errors. Yes, I factory reset before restoring. It seems that this TWRP is not doing everything like it used to under the 4.2's. I'm going to go back to CWM and restore a CWM backup, regroup, recharge.......and try again from scratch to test this thing out again. Wish me luck.
Click to expand...
Click to collapse
Best of luck to ya! I have restored my nandroid with twrp but not in my latest version. I'll give it a try this evening and see what happens on my end. I have not used the aroma installer because I personally would rather not use it. I just use the camera fix from Pollution since I don't have the screen flicker or any other issues with my phone.
I used F2FS file system on data and cache partition and now its like i have a nexus 6p there is little to no UI lag or even any delay in opening apps.
Used to use F2FS on my previous devices(lg g2, Galaxy S2 and Xperia Z ultra) and man the effect was noticeable from day1, so tried it on this device and guess what it works flawlessly.
Here is a thread for comparition between F2FS vs EXT4(the default one).
So here is guide for you guys its Highly dangerous setup so please follow this if you know how to restore a SoftBrick status.
Caution:--
ONLY FOR CM13 and N based roms which support F2FS, If used on OOS3 or H2OS(mm) it will result in not converting the data/cache partition properly and will end up 0mb partition because of modified twrp used for these roms and you wont be able to be mount your internal memory too.
Backup backup backup. Make sure you take a backup and save it on your pc before performing the steps.
Things you can do to make your life easier:--
Clean flashing of rom is highly recommended but you can try dirty too as it does not touch the system partition but still clean is preferred.
Use ZipMe app to make a zip file for your apps so that installing all those apps becomes easier if coming from clean flash.
Full backup of your internal memory files as this setup formats even your internal memory even if you select only the data partion.
Best stay on stock kernel as there is no mention of any cm13 custom kernel to have f2fs support. They may have but in any thread of these i couldnt find f2fs word anywhere. So stay stock.
Rom compatibility/tried on:--
Exodus.
All cm13 based roms work flawlessly.
LineageOS14
Kernel compatibility:--
Darkbeast
Stock kernel or the one provided by default by the rom.
Yarpin's kernel.
Benschold kernel.
Note:- Please this method has worked on F2FS supported roms only before following any of it make sure your rom developer has incorporated f2fs support in his/her rom.
Steps:--
Use revert2lollipop to revert back to lollipop firmware if you are on OOS3/H2OS and wanna try f2fs.
Download and upgrade your twrp version to latest.
Copy the .img file to your root folder and reboot to twrp select--->Install-->Install images button-->select the new .img file you copied and reboot to recovery.
Format everything including your internal memory.
Go to advance wipe and select cache partition and select repair and change file system, once there select change file system and change it to f2fs and swipe. Images.
Repeat the above step for data partition.
Go to twrp settings and tick rm -rf, this will make your device retain your f2fs system after clean flash of some roms.
Reboot your recovery once and copy back all your data back to your internal memory.
Flash the required modem for your rom and clean flash your rom for the best bug free experience.
Benefit!
PS:- Please if someone daring does use this on another rom and if everything works flawlessly then please post about it, i will add it compatible roms/kernels.
Press thanks if it worked for you and do post about any improvements you saw.
Credits:-
@Androguide.fr
@ opt devs for awesome roms.
@ jrummy Apps for zipme app.
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
jbarcus81 said:
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
Click to expand...
Click to collapse
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
So we need stock kernel
isoladisegnata said:
So we need stock kernel
Click to expand...
Click to collapse
Yeah for now, since for f2fs roms to work properly the kernel also needs to support the file system and no custom kernel has f2fs as a feature mentioned in their list. I couldnt find anything related to f2fs even with the search function, will update the thread if f2fs support is confirmed by the devs of the respective kernels.
chintu1234 said:
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
Click to expand...
Click to collapse
Yeah.. Not using any kernel other than what's built into AICP from the OP.. :highfive:
Added yarpin's kernel to the compatible kernels.
Using AOKP with stock kernel perfectly! Thanks for this OP and also for sharing the ZipMe app! Which is amazing, Didnt work for me on CM13 though but love the idea! JRummy devs make the best apps
Can i use titanium backup to app+data?
isoladisegnata said:
Can i use titanium backup to app+data?
Click to expand...
Click to collapse
Yes you can.
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
isoladisegnata said:
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
Click to expand...
Click to collapse
Yeah if you connect to PC after conversion you will be able to access your memory as you used to with default system.
Just make sure to wipe system,data,cache,dalvic,internal before going any further for good measure.
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Tatsuya_ said:
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Honestly I wouldn't notice a difference unless you put 2 phones running ext4 and f2fs side by side for comparison. But if I were to really force an answer out from myself I would say that app opening and switching times are greatly reduced.
you really deserved more thanks for this guide.. keep it up and great work!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
Nice! thanks for reporting, will add to OP.
Works great with Exodus ROM !!!
very good. Thank you very much. wonder why only cache and data? What about the system partition?
rakieta said:
very good. Thank you very much. wonder why only cache and data? What about the system partition?
Click to expand...
Click to collapse
It really isnt needed because in system partition most of the time only read function is done while data and cache constantly need read/write functions to be performed so you wont notice anything different if you format system to f2fs.
So I tried the Flash TWRP recovery version 3.0.3-1 and found out that it can format the cache partition to f2fs without any error. It also persistent across reboot. Been running since morning and don't see any issue with performance. So I see this as big step forward for Nexus 6p phone. My device have data and cache are running on F2FS and with the flash kernel.
ll
minhgi said:
So I tried the Flash TWRP recovery version 3.0.3-1 and found out that it can format the cache partition to f2fs without any error. It also persistent across reboot. Been running since morning and don't see any issue with performance. So I see this as big step forward for Nexus 6p phone. My device have data and cache are running on F2FS and with the flash kernel.
Click to expand...
Click to collapse
where did you get 3.0.3-1 if you don't mind me asking?
And doesn't f2fs not play so well with supersu? And i heard, on the 6p, f2fs isn't any faster than ext4.
Check the flash kernel page at the end of the thread. The Flash had a link that point to his own personal site. It should be located in the TWRP folder. Anyway, I didn't link it directly since he have gone private at the moment.
I am using the latest SuperSu 2.79S3.
Does it work with pure nexus?
minhgi said:
Check the flash kernel page at the end of the thread. The Flash had a link that point to his own personal site. It should be located in the TWRP folder. Anyway, I didn't link it directly since he have gone private at the moment.
I am using the latest SuperSu 2.79S3.
Click to expand...
Click to collapse
His personal site that you directed me to does not have that link. All it has is a link for his kernel. Would you please PM me the exact link?
TrainNanpaMaster said:
His personal site that you directed me to does not have that link. All it has is a link for his kernel. Would you please PM me the exact link?
Click to expand...
Click to collapse
It's definitely there.
Sent from my Nexus 6P using Tapatalk
minhgi said:
It's definitely there.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It's not the official link. Might be an unofficial release.
The Frustrated Indian said:
It's not the official link. Might be an unofficial release.
Click to expand...
Click to collapse
Official TWRP does not support F2FS. You need this version made by The Flash (XDA moderator) in order to use F2FS, along with a ROM and kernel that support it. He's been supporting F2FS TWRP for some time now. That's his personal website.
So /system is useless since it's 'read-only' 99% of the time (this was Flashes findings he posted in his thread, feel free to search it yourself). He did note that he saw significant speed improvements in his testing for /data.
If you do decide to give it a try, you'll probably want to back up all of your data and decrypt your phone by formatting userdata. Older releases of Flashes F2FS TWRP do not support encryption. Even if your pattern/pin/pass is correct TWRP will say it's not and won't let you in. I haven't tried that newest release, but I did on the older ones. Maybe someone else could speak to encryption on 3.0.3-1. Aside from that, converting from F2FS will format your internal SD regardless, even if his TWRP works on encrypted devices. So back up and give it a shot.
Edit: if anyone stumbles upon this, Flashes 3.0.3-1 DOES work on encrypted devices now.
which rom are you on ?
As long as you use flash kernel, you can run any rom besides stock with f2fs. Ive used almost every rom for our phone with f2fs. There are quite a few unofficial versions of twrp that supports f2fs. The 3.0.3.. versions are really slow at restoring nandroid backups for some reason. I use multi rom twrp. I forget the version, its 3.0.2-2 i think.
Cache
It's official. I'm now a BELIEVER.
In F2FS.
I finally took the plunge and converted to it.
To anyone that I showed doubt to in regards to f2fs, I sincerely apologize. It is indeed noticeably faster than ext4. Apps fly open now, everything is glassier, and snappier. There is definitely a profoundly noticeable difference over ext4. In fact, it really feels like I have a new device. The best way I can explain it - is that the phone feels like it's running at a constant 60fps now.
I was able to move my ext4 nandroid over to my freshly partitioned f2fs 6p. This saved HUGE amounts of time setting everything back up. I just had to copy over TWRP backup (and restore) the DCIM folder, as well as my titanium backup folder, along with all the standard rom stuff like gapps, rom, kernel etc.
All in all, I'm extremely impressed with f2fs. On paper, it looks to be only marginally faster than ext4. But in real life, you can definitely see a big difference. Now a believer.
Ok, so I took the plunge into this F2FS thing. I followed this tutorial. Wiped everything including internal cache, converted to f2fs. Now, I'm trying to copy rom and gaaps from pc to phone by mounting system and data but having issues. My pc can see the phone in explorer but can't seem to copy. screenshots below.
Any help would be greatly appreciated.
EDIT: silly me, forgot to reboot the recovery lol.
TrainNanpaMaster said:
It's official. I'm now a BELIEVER.
In F2FS.
I finally took the plunge and converted to it.
To anyone that I showed doubt to in regards to f2fs, I sincerely apologize. It is indeed noticeably faster than ext4. Apps fly open now, everything is glassier, and snappier. There is definitely a profoundly noticeable difference over ext4. In fact, it really feels like I have a new device. The best way I can explain it - is that the phone feels like it's running at a constant 60fps now.
I was able to move my ext4 nandroid over to my freshly partitioned f2fs 6p. This saved HUGE amounts of time setting everything back up. I just had to copy over TWRP backup (and restore) the DCIM folder, as well as my titanium backup folder, along with all the standard rom stuff like gapps, rom, kernel etc.
All in all, I'm extremely impressed with f2fs. On paper, it looks to be only marginally faster than ext4. But in real life, you can definitely see a big difference. Now a believer.
Click to expand...
Click to collapse
Somehow my nandroid backup of lineage os wiped internal storage again (I restored after formatting /data and /cache to f2fs). Ended up doing clean install.
Anyone tried this using custom kernels? whenever i seem to flash a custom kernel nathans TWRP throws the error of either ramdisk unpack failed or recovery busybox problem.
xSilas43 said:
Anyone tried this using custom kernels? whenever i seem to flash a custom kernel nathans TWRP throws the error of either ramdisk unpack failed or recovery busybox problem.
Click to expand...
Click to collapse
I use a kernel that i think is even better than flash kernel (IMO). It's fundamentally identical to Uber kernel, but made by a team member. He also makes uberstock nightlies which is the best ROM in my opinion because it's gcc 6.3.1 and clanged to 3.9.1. Combined with F2FS, and it's pure glassy snappy butter multiplied to power level 9000.
I've literally flashed every single ROM including PureNexus, and these kernel and nightlies absolutely teabag everything I've tried.
Silas i know you know about this already, but The kernels and nightlies can be found here:
https://temp.bbqdroid.org/
TrainNanpaMaster said:
I use a kernel that i think is even better than flash kernel (IMO). It's fundamentally identical to Uber kernel, but made by a team member. He also makes uberstock nightlies which is the best ROM in my opinion because it's gcc 6.3.1 and clanged to 3.9.1. Combined with F2FS, and it's pure glassy snappy butter multiplied to power level 9000.
I've literally flashed every single ROM including PureNexus, and these kernel and nightlies absolutely teabag everything I've tried.
Silas i know you know about this already, but The kernels and nightlies can be found here:
https://temp.bbqdroid.org/
Click to expand...
Click to collapse
yeah that's the kernel i normally use, however, i tried using r48 and r49 still get the same error, i even tried flash's kernel and I'm getting the same error, guess ill just stick with stock kernel for now. Very weird it worked fine for you but not me.
EDIT:
Somehow when i decided to try reflashing except not using SuperSU the kernel was able to flash.
Try a different twrp. The multirom twrp supports f2fs and a few more. Ive tried alot of them and never seen an error like yours.
TrainNanpaMaster said:
I use a kernel that i think is even better than flash kernel (IMO). It's fundamentally identical to Uber kernel, but made by a team member. He also makes uberstock nightlies which is the best ROM in my opinion because it's gcc 6.3.1 and clanged to 3.9.1. Combined with F2FS, and it's pure glassy snappy butter multiplied to power level 9000.
I've literally flashed every single ROM including PureNexus, and these kernel and nightlies absolutely teabag everything I've tried.
Silas i know you know about this already, but The kernels and nightlies can be found here:
https://temp.bbqdroid.org/
Click to expand...
Click to collapse
why is this rom and kernel not on xda???? or maybe i havent spotted it..... it is SUPER SMOOTH, in F2FS it is running amazing... didnt mess with the kernel at all, and this thing is fire!!!!
i42o said:
why is this rom and kernel not on xda???? or maybe i havent spotted it..... it is SUPER SMOOTH, in F2FS it is running amazing... didnt mess with the kernel at all, and this thing is fire!!!!
Click to expand...
Click to collapse
It's fundamentally very similar to Uberstock ROM and kernel.
A lot of people on these forums think Purenexus is the best rom ever. (most likely because the developer really branches out with social media and branding).
They obviously haven't tried this or uberstock.
Introduction
Hello all, this is my version of TWRP for the Nexus 6P, which includes the ability to convert your /data and /cache partitions to F2FS. This will stay inline with TWRP's changes for the most part, the changes will be listed below.
What in the world is F2FS?
From Wikipedia:
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
F2FS was designed on a basis of a log-structured file system approach, which it adapted to newer forms of storage. Jaegeuk Kim, the principal F2FS author, has stated that it remedies some known issues of the older log-structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. In addition, since a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), it supports various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
Click to expand...
Click to collapse
Before diving into this, I would recommend reading the official F2FS documentation to understand why this may be good for you. This is potentially unstable, F2FS is a file system that is very much in active development. There is a reason that most OEMs go with ext4 out of the box. But I digress, I am NOT here to sell you on F2FS; it makes zero difference to me if you use it or not, I am merely providing you with a tool to do so.
Changelog + differences
Differences:
f2fs-tools bumped to 1.7.0 (Omni's 6.0 branch is on 1.4.0)
TWRP app installation offer disabled by default
Conversion procedure
Download TWRP from the link above
Grab a kernel that supports F2FS (I use my own as I know it works)
Back up any important data as this will wipe your entire internal storage
Boot into the bootloader and flash the recovery
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then hit "Change or Repair File System"
Hit Change File System
Choose F2FS and slide to confirm
Repeat the previous three steps for cache
Reboot and move all of your files back over (if restoring through TWRP, make sure to check the option to use rm -rf instead of formatting)
If you have any issues with this, you may need to ask your ROM developer to merge the two commits below.
Bug reports
You are NOT in ANY circumstance to report ANY bugs to the TWRP team.
If you have an issue with flashing something in TWRP, copy the recovery log to your sdcard and post it here.
If swapping to F2FS does not stick, try formatting your data with TWRP (Wipe > Format Data) or fastboot format userdata first.
If your phone does not boot after swapping to F2FS, either your kernel or ROM does not have proper support; post in their thread.
Additionally, check out some of these helpful posts:
https://forum.xda-developers.com/showthread.php?p=70699197
https://forum.xda-developers.com/showthread.php?p=71074016
Adding support to ROM
In order to properly support the initial conversion to F2FS, please add these two commits to your source:
https://github.com/omnirom/android_system_core/commit/1c6700a8fb31c6e314df4f031fa23fa9178c7ca7
https://github.com/omnirom/android_system_vold/commit/c879edb2fecae709f404c2d71c1d47ceac3a325e
The reason some people have issues converting is fs_mgr will try to read the block device as ext4 and destroy the f2fs block. This commit skips that check, allowing F2FS to pass through.
Sources
TWRP is licensed under GPLv3, meaning my changes must be disclosed. I also inline a custom kernel so that source is included as well. I also add in the other repos I modify.
Recovery: https://github.com/nathanchance/android_bootable_recovery/tree/android-7.1
Kernel: https://github.com/nathanchance/angler/tree/7.1.2-flash
Device tree: https://github.com/nathanchance/twrp_device_huawei_angler/tree/android-6.0
f2fs-tools: https://github.com/nathanchance/android_external_f2fs-tools/tree/android-6.0
First!
Thanks for the recovery. Been using it with flash kernel. I see considerable performance improvement in asphalt Xtreme game( idk if its the f2fs or kernel ).
Nice !!! :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you, and thank you for the exemplary GPL compliance. It's noticed and appreciated.
Now this is awesome... On it, will report soon
Much appreciated!
Sent from my Nexus 6P using Tapatalk
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Nitrogen : yes
Somebody must report it and i will update my post.
ThNks
ariefabuzaky said:
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Somebody must report it and i will update my post.
ThNks
Click to expand...
Click to collapse
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Worked perfect! Thanks Flash!!!
I tried this with PN and am now stuck in a boot loop. I flashed the twrp with F2FS support then tried to change the file system followed by installing the latest vendor, latest flashable bootloader+radio, latest pure nexus and gapps, flash kernel, and latest su. Didnt work. Im not stuck in a boot loop I cant get out of. Ive tried every combination of the above. I also tried restoring my backup but that gives me an error. I also tried changing the file system back to ext4. Nothing works. Anyone experience this or have any suggestions?
---------- Post added at 09:09 AM ---------- Previous post was at 08:58 AM ----------
jochem86 said:
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Click to expand...
Click to collapse
Im in the same boat.....what steps did you do to get back to stock?
Data keeps reverting back to ext4 after 1st boot.
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
Mine too....Im stuck in a bootloop. Are you?
Whats also weird is switching too f2fs wiped my storage but once the data reverted back to ext4....my original storage came back too!! Im not sure how or why that is happening either.
I just followed OP and formatted everything first, now i have SAOSP running with flash on f2fs..
Works great, so far it doesn't feel like a huge improvement though..
Sent from my Nexus 6P using XDA-Developers Legacy app
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
What makes you say that?
Back then when I was using Temasek on my Note 3, he incorporate a script that automatically format the system partition to F2FS when flashing his ROM. That is if the system partition is already in f2fs and I think that was pretty amazing but short live. I wonder if other ROM developer could go the same route if formatting F2FS system was popular enough. That would make updating new rom one step easier. Just for thought.
---------- Post added at 09:38 AM ---------- Previous post was at 09:16 AM ----------
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
minhgi said:
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
Click to expand...
Click to collapse
I wish you told this earlier....This is exactly what happened and I had to clean install
NoobInToto said:
I wish you told this earlier....This is exactly what happened and I had to clean install
Click to expand...
Click to collapse
It wouldn't matter though, I get a warning that the backup was made with EXT4 and that backup may not boot unless changed back to it
Iceburn1 said:
What makes you say that?
Click to expand...
Click to collapse
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
Exactly doing the same....
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
That's too bad its not working for you, its working on my side no problem, did you format in twrp if its not sticking? Im on RR with Flash kernel.