yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] erk1725:
Has anyone managed to get any of the recent nightlies from Vanir for toro to run on f2f? I'm specifically interested in primes Vanir? I'm not sure the date of the release that a bunch of f2f stuff was mentioned in the change log, I think it was around 6/14? Anyways, I tried to flash it with Philz from smitty and the 6/9 kernel from smitty but it never booted and really took me a long time to get my phone back up and running after trying to flash it. My backups were gone obviously from the wipe/format to f2f and I somehow lost recovery along the way which was really hard for me to get back. Currently running the 6/17 nightly of Vanir on ext4 with smitty 6/15 and have smitty twrp 2.7.1 f2f but am very concerned to try to convert it over to f2f again in case it doesn't work

Hope that all made sense

Any help is greatly appreciated!! You guys are awesome!!

Edit: looks like the change logs from 6/8 and 6/11 mention adding f2f
[Samsung Galaxy Nexus] bsmitty83:
it should be fine , as long as do the steps to convert the ROM to f2fs ( changing the updater script ) it should work OK .

as for the troubles you were having , you can't go wrong copying everything off your sdcard onto your computer via adb pull . it will take a long time for it to copy it all if you have alot of data but let it run and it will work . as for reflashing a recoverey , again simple to do with fast boot . take the recovery.IMG out of the zip package and you can fastboot flash it like anything else .

basically to convert your daily driven phone to f2fs , the best advice I have is to learn to use adb and fastboot . they are invaluable if you mess something up . I've never been in a situation where I couldnt recover my system easily using those 2 tools . back up what you consider valuable and there should be no worries .

Hack the Tuna
[Samsung Galaxy Nexus] Danny1976:
Can you upload F2FS-Compatible Slimkat v5.9? Thank you.
[Samsung Galaxy Nexus] latenightchameleon:
For sure. Check my signature.

Changes:

- trimmed system apps for best performance

- latest DirtyV SuperRam kernel (6/15)

- 320 DPI

Re-add anything from the original if necessary.
[Samsung Galaxy Nexus] erk1725:
Thank you Smitty, I did end up giving myself a crash course with adb and fastboot to get my phone to boot but I ended up having to more or less go back to stock and this is how I ended up back on ext4. I guess updated the updater script is where I'm not sure what to do? Thank you for the reply. So nobody has managed to boot any of primes vanir in f2f?
[Samsung Galaxy Nexus] Danny1976:
Thank you. How do you convert it to F2FS? I don't want to be bothering you for the converted version everytime there is a new weekly release.
[Samsung Galaxy Nexus] latenightchameleon:
I manually edit the updater-script and make a few changes in the ROM for myself. Oh and don't worry about it, just check this thread or my signature within a day after a slimkat release ; I've had the f2fs-converted version right after 5.9 released, just forgot to upload it :good:
[Samsung Galaxy Nexus] bsmitty83:
you should be able to pull the meta-data folder and boot.IMG from the f2fs version of commotio vanir that [MENTION=2838735]aosp[/MENTION] built as the original test ROM , and insert it into the atom ROM zip . it will say commotio when you flash it but you'll know its not lol . there is all the info to replace the lines in the updater script in the op of this thread and all over the place over in my thread or just about any f2fs cooked version of any ROM .

Hack the Tuna
[Samsung Galaxy Nexus] erk1725:
Thank you, I will read up on the updater script stuff and try to give it another shot

Thanks again!
[Samsung Galaxy Nexus] erk1725:
Thank you!! This worked perfectly!! No issues!
[Samsung Galaxy Nexus] pianistaPL:
Thanks for this!

BTW which lines in updater script did you change? Only

and

or something yet?
[Samsung Galaxy Nexus] victor2868:
Guys, just now I'd try the method of you for my carbon rom, but I facing some problem, I have been replaced the boot.img from dirty v kernel and replaced updater script to carbon rom packages but when I flashing it using by twrp f2fs, It said failed:confused:
[Samsung Galaxy Nexus] davluc:
Flashed this, but location not working. Anyone experiencing this?
[Samsung Galaxy Nexus] Punkiderma:
Have you replaced the files without extracting or you have extracted, replaced and then repacked the zip?

If you extract and repack, it won't flash, don't know why.

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] victor2868:
Stuck at the google logo there and I noticed that when I flashing the carbon latest version with the boot.img and updater.script provided by akhi24nick, the partition will be changed to ext4 automatically, do you have this problem?:)
[Samsung Galaxy Nexus] latenightchameleon:
Install fusedlocation.apk (attached) :good:

Pretty much all the formats, mounts, and whatever else ext4
[Samsung Galaxy Nexus] Punkiderma:
How did you noticed that? Is that script for carbon?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] massoudsh:
hi guys...which rom(s) is(are) full support F2FS at this time? plz give me link of them:confused:
[Samsung Galaxy Nexus] _hz:
has someone converted the latest Slimkat weekly 5.9? maybe without removing anything?

tried it myself with this tool but it's stuck on the google logo. used dirty-v kernel, surely did something wrong... :cyclops:

http://xdaforums.com/nexus-4/development/script-convert-rom-to-f2fs-t2731652
[Samsung Galaxy Nexus] KShion619:
Did anyone attempt editing this Patcher?

I attempted it myself and failed
[Samsung Galaxy Nexus] poo706:
Not that I'm aware of. I can take a stab at it early next week, but I'll need a tester because I haven't converted to f2fs.

[poo]
[Samsung Galaxy Nexus] victor2868:
After flashing the carbon rom
[Samsung Galaxy Nexus] Punkiderma:
Yes...

But how did you saw that the file system was ext4 and not f2fs?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] victor2868:
After flashing the rom package, u checking the file system at advance->ext4/f2fs switch, u will see the system has been switched from f2fs to ext4
[Samsung Galaxy Nexus] Danny1976:
Slimkat 5.10 Kitkat 4.4.4 just came out. Let me know when you convert it to F2FS, thank you.
[Samsung Galaxy Nexus] poo706:
[MENTION=4576677]KShion619[/MENTION] and others:

I whipped up this EXT4 to F2FS converter batch script for Windows. It looks to be working correctly, but I haven't converted to F2FS, so I can't totally test it. It's rather dumb and doesn't check for this and that, but it gets the job done and it's WAY simpler than the grouper conversion tool that inspired this.

Instructions:

1) Unzip EXT4_to_F2FS_gnex.zip to any empty folder, make sure there are no spaces anywhere in the path.

2) Place your EXT4 gnex ROM zip in the same folder, make sure there are no other zips in this folder.

3) Run EXT4_to_F2FS_gnex.bat.

Thread: http://xdaforums.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702

[poo]
[Samsung Galaxy Nexus] massoudsh:
Where i can find f2fs version of vanir rom?!
[Samsung Galaxy Nexus] Danny1976:
I'll try today and let you know how it worked.
[Samsung Galaxy Nexus] latenightchameleon:
Check the signature. This time I've made no changes to the original, except F2FS-compatibility:good:
[Samsung Galaxy Nexus] massoudsh:
Plz answer me..?
[Samsung Galaxy Nexus] poo706:
Everybody drop what you're doing and hook massoudsh up, it's already been 5 hours for god's sake.

[poo]
[Samsung Galaxy Nexus] Danny1976:
How do you update to the new weekly? I did a dirty flash by wiping the dalvik cache/cache and then installing the ROM. But the custom TWRP seems to be affecting the update. I did go to settings and made sure the check mark was on force data and cache wipe to F2FS and I unchecked the include system since I am doing a dirty flash. Right now my phone is stuck on the Google logo with unlocked. Recovery is not there anymore, just odem.

edit: I rebooted and was able to access recovery. Will try to install rom again. Just figured it out....I needed to flash the Smitty Kernel with the ROM.
[Samsung Galaxy Nexus] miesfu:
I've downloaded your file, will try when the PA 4.4.4 releases, saying today.

will update you.
[Samsung Galaxy Nexus] _hz:
works like a charm!

:good:
[Samsung Galaxy Nexus] latenightchameleon:
You didn't have to format and wipe all that. Just dirty flash over what you've got. The latest f2fs-compatible DirtyV kernel is already included, so no need to flash that. Glad you figured it out tho :good:
[Samsung Galaxy Nexus] miesfu:
Just downloaded latest PA4.4.4 http://download.paranoidandroid.co/roms/maguro/ version 0625

and use your tool to convert to F2FS version

Flashed converted version, then flashed 0615-Dirty-V kernel

No problem found now

thanks for your great job...
[Samsung Galaxy Nexus] poo706:
Thanks for the feedback, I appreciate it. Did you flash the converted ROM and dirtyv all in one recovery session?

[poo]
[Samsung Galaxy Nexus] miesfu:
As I faced problem when flashing ROM and Kernel in one session last time, I flash as following process:

Flash ROM-----without reboot...

then choose Kernel and flash...

Reboot...

Everything goes well

BTW, ART still makes some app FC, so I don't use ART run time
[Samsung Galaxy Nexus] poo706:
It's that "without reboot" information that I was looking for. You used my tool to edit the installer script and replace the ext4 kernel with a f2fs kernel, but then after flashing drityv, you replaced the kernel again. Would you mind making a nandroid and try installing just the converted ROM so that I can be sure that the included kernel boots?

[poo]
[Samsung Galaxy Nexus] miesfu:
Just tried,

Re-flash the converted ROM and reboot...goes fine...

then I checked the kernel using in your tool-kit, it's Dirty-V Jun. 9 version :)

So, in short:

can just simply use your tool to convert, then flash
[Samsung Galaxy Nexus] poo706:
Thanks for doing that! Looks like rk used dirtyv for his 6/14 F2FS builds he put out, which is where I got the boot.img from.

[poo]
[Samsung Galaxy Nexus] miesfu:
One question:

Can I replace your kernel with the one from Dirty-V 6.15 version, then do convert...then I flash ROM to directly upgrade to the latest dirty-V kernel? no need to flash kernel once again.

Or I need to change some script as well besides replacing the kernel? I've no idea about this.

Thanks
[Samsung Galaxy Nexus] Hetalk:
[MENTION=3927368]poo706[/MENTION] .. your tool worked pretty well for the latest paranoid. Thanks buddy.

---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------

Just replace "boot.img" from the zip file, with the one you extract from kernel of your choice. :good:
[Samsung Galaxy Nexus] poo706:
I think I understand what you're saying, and I would love if you'd test it out for me. Remove boot.img from the folder that the conversion tool is extracted to. Extract boot.img from dirtyv 6/15 into the conversion tool folder. Run the tool on an EXT4 ROM like normal and see if it boots.

[poo]

---------- Post added at 10:18 AM ---------- Previous post was at 10:16 AM ----------

Excellent! I'll create threads for the tool today. Thanks for testing.

[poo]
[Samsung Galaxy Nexus] miesfu:
Clear....thanks
[Samsung Galaxy Nexus] dbh369:
I wanted a to link a post here talking about mounting with discard if fstrim isn't working just fyi.

http://xdaforums.com/showthread.php?p=53677028

Note, link there for a hopefully full fstrim enabled LS too.
[Samsung Galaxy Nexus] massoudsh:
o noob question...

how to detect file system type using terminal in android?
[Samsung Galaxy Nexus] poo706:
Just type "mount". You don't need to do "su" first. Use "grep" to narrow the results. For instance, if you want to verify that you've reformatted to F2FS correctly, type "mount | grep f2fs".

[poo]
[Samsung Galaxy Nexus] massoudsh:
tanks you very much!! today i convert last release of vanir rom to F2FS using your tools & this is my result:

everything is ok & i am very happy...tanks again man:good:
[Samsung Galaxy Nexus] DriftGT:
How can we do TRIM with f2fs? The app lagfix says not compatible. Any help? Now I am using ext4 again because my phone become very slow with low read write speeds and the lagfix didnt work. Any help for that?

Enviado do meu Galaxy Nexus através de Tapatalk
[Samsung Galaxy Nexus] poo706:
There was a bunch of chatter about it in the dirtyv thread for a while, but then everyone just dropped it. I've seen [MENTION=4544860]osm0sis[/MENTION] say a few times that untrimmed f2fs is still better than trimmed ext4. I also saw something about a potential benefit to mounting f2fs volumes with the discard option.
[Samsung Galaxy Nexus] osm0sis:
Mounting with discard will avoid the need for manual trimming altogether, and apparently f2fs backburners the discard until after the main R/W has completed, to avoid the choking we'd see on ext4 and keep the speed up, but I'd still personally prefer to get manual f2fs trim working correctly like it does on Linux. That way we know we're running as fast as we can with no hitches, and making use of Android's built-in fstrim scheduler (put there for this purpose).

And yeah, you wouldn't see any effects from not trimming on f2fs until your entire storage had been filled (meaning that even when you delete something the blocks are only marked erased and are still technically full), since your last format. f2fs uses completely empty blocks first, whereas ext4 goes for the first marked erased blocks it finds causing the bottleneck almost immediately. After that you'd still run into the bottleneck like you would on ext4, but I think f2fs would still be faster untrimmed, and after hitting the bottleneck, than ext4 is manually trimmed regularly. So I definitely think there's a bit of placebo effect going on for some folks. ;)
[Samsung Galaxy Nexus] CelticRT:
Help!! Emergency!! I like my galaxy nexus and I cannot let it die like this..

I rooted my galaxy nexus and installed paranoid android 4.4 on it.. im used to odin since i used to have a samsung device. Unfortunately I formatted my phone through recovery and every files was gone. no backup or nandroid backup that was created in my laptop since it froze. Stuck in boot logo and went to twrp and when i exited there was no os installed. I tried to use Wugfresh Nexus Root Tool to restore the stock rom but the most unfortunate thing was my laptop cannot recognize that it is on adb. I have Windows 8.1 Update 1 and it says Device Descriptor Request Failed (not working properly) so i tried to repair and uninstall the drivers of nexus but it also needed adb which is not working on my laptop and other laptops that i currently used. the adb and fastboot mode are there but all my laptop and devices cannot recognize it.. please help me to restore the galaxy nexus to normal.. I will appreciate it so much :) Thank you for time and cooperation
[Samsung Galaxy Nexus] amd_h4x0r:
try this to get adb & fastboot working http://xdaforums.com/showthread.php?p=48915118
[Samsung Galaxy Nexus] CelticRT:
Forced close!!

I did that already but the problem is my windows 8.1 computer wont recognize my device... i have adb and fastboot already preinstalled but since my device formatted all files and the os were formatted which means there is no os installed, is there anyway to enable android debug through recovery or fastboot or something like that, because i cannot start my phone... its stuck in bootloop and os were uninstalled.....from the tool that you shared at me.. i was on administrator privileges and when i press yes.... it forced close by itself.
[Samsung Galaxy Nexus] latenightchameleon:
Do you have the right fastboot/adb drivers? Can you boot into recovery?

Regarding the drivers:

Install them and restart the computer

Go to Device Manager, find the device, and select Update Driver Software.

If it doesn't detect automatically, select Browse my computer for driver software

Select Let me pick from a list of device drivers on my computer

Select ADB Interface from the list

Select SAMSUNG Android ADB Interface (this is a signed driver). If you get a warning, select Yes to continue.

Done!

Try booting into recovery or bootloader if you can, rest is easy after you've got fastboot/adb working.
[Samsung Galaxy Nexus] CelticRT:
it says unknown device (device description failed)

The problem is my computer wont recognize my device also my device has not enabled usb debugging since data was formatted and no os installed. Also I installed the drivers and everything but Android ADB Device Interface is not showing in device manager.....or any drivers from galaxy nexus.. i tried your method but the driver that only showed was Unknown USB Device (descriptor failed) also i tried to uncheck the box of (list of compatible hardware) there was bunch of drivers... i tried samsung usb device but nothing changes... please someone help! I just want my device to have an os installed at least and everything working..
[Samsung Galaxy Nexus] latenightchameleon:
Did you uninstall the existing driver before installing the new one?
[Samsung Galaxy Nexus] CelticRT:
All the existing drivers that resembles to nexus. The weird part is I installed all the drivers but its not showing in USBdeview (list of drivers) I checked if the drivers are installed but it was no there. The only device that showed was unknown USB device (device descriptor failed)

---------- Post added at 05:07 AM ---------- Previous post was at 05:02 AM ----------

The drivers such as android adb interface is not showingbon device manager. Does that mean something.?
[Samsung Galaxy Nexus] latenightchameleon:
Try repeating this step:

Go to Device Manager, find the device, and select Update Driver Software.

If it doesn't detect automatically, select Browse my computer for driver software

Select Let me pick from a list of device drivers on my computer

Select ADB Interface from the list

Select SAMSUNG Android ADB Interface (this is a signed driver). If you get a warning, select Yes to continue.

Done!
[Samsung Galaxy Nexus] CelticRT:
My device is on the verge of death...

Maybe it is time to be responsible and accept my device is already dead and cannot be revived....my recovery used to work but now is stuck at bootloop but blinking.......Also i reinstalled my unknown device but this time it is also stuck at the progress bar of finding devices...do you think someone can fix this for a $100 or is it better to buy another phone?
[Samsung Galaxy Nexus] GuinnessX:
Has anyone tried to get the Mpokang kernel to work with F2FS? If not, is there a general guide to adding S2FS support to a kernel if I want to compile it myself? (I'm not a dev)
[Samsung Galaxy Nexus] neilrl79:
I have been unsuccessful in finding a recovery for Toro that has the F2FS option, can someone point me in the right direction?

Sorry for the noob question but I've been looking for a couple days and can't find an answer.
[Samsung Galaxy Nexus] poo706:
See posts #1 and #2 here: http://xdaforums.com/galaxy-nexus/development/kernel-dirtyv-6-9-14-t2613655 .

[poo]
[Samsung Galaxy Nexus] neilrl79:
I have been through those posts several times but the only recovery I found was for maguro. I must be missing it.

I thought maybe TWRP-TUNA-F2FSALL.IMG was it but when I had it installed and tried to flash a ROM it said the flash failed because I had a Maguro and was trying to flash a Toro ROM.
[Samsung Galaxy Nexus] poo706:
In post #1 there is a section for recoveries and there are 4 of them there, one is just for toro.

[poo]
[Samsung Galaxy Nexus] neilrl79:
The recovery in post #1 for toro doesn't have the option to format the partitions to F2FS under the advanced menu.

[IMG="pic of recovery"]http://i857.photobucket.com/albums/ab139/neilrl79/Mobile%20Uploads/IMAG0025_zpskfwyfzhy.jpg[/IMG]
[Samsung Galaxy Nexus] poo706:
You should probably just post in that thread. All I know is that there's a bunch of recoveries in that thread and I thought that's what everyone was using.

[poo]
[Samsung Galaxy Nexus] neilrl79:
OK dude, thanks for trying to help me.
[Samsung Galaxy Nexus] amd_h4x0r:
This might be a bit off topic but ever since switching to F2FS and ART, I have had issues with AdAway. It will download and apply the host file, but after a reboot it is always disabled and doesn't block ads. Any thoughts?
[Samsung Galaxy Nexus] poo706:
If you're on liquidsmooth, it's probably because of the built in ad blocker.

[poo]
[Samsung Galaxy Nexus] amd_h4x0r:
Yeah, I just noticed the built in one. It seems to be working too. I guess I'll run with it instead of AdAway.
[Samsung Galaxy Nexus] Devil Trigger:
What are the benefits right now after the f2fs conversion on our Gnex?
[Samsung Galaxy Nexus] mrgnex:
This has been answered several times before.. It gives better i/o performance.
[Samsung Galaxy Nexus] Devil Trigger:
Yeah, i know this, but in daily usage is there difference?
[Samsung Galaxy Nexus] mrgnex:
Well unless you read/write some files everyday not much. Apps launch faster I guess. I had to format my phone so I think it is faster anyway.. Try it and see for yourself :)
[Samsung Galaxy Nexus] Devil Trigger:
Thanks :D
[Samsung Galaxy Nexus] ILA:
How do I check my partitions to see on what format they are? (f2fs or ext4)
[Samsung Galaxy Nexus] poo706:
From a terminal, type:

mount | grep f2fs

If you get 3 lines as a response, you're all f2fs, if you get nothing you're ext4.

[poo]
[Samsung Galaxy Nexus] samedi:
I'm wondering if anyone came across a similar issue to mine. I was having issues with finding TRWP that would have the option to convert to f2fs enabled. The official one did not work and the only one that did was the generic one 2.7.0.0 from dirtyV Kernel thread. I converted all the filesystems to f2fs but although it said it finished successfully the /system partition had some issues as it would not show in mount at all. Neither as an ext4 nor f2fs. I could access it and copy files to it but could not copy files from it plus after a reboot the copied files would not show anymore. Flashing any kernel would not error out but the /system be reverted to ext4.and the rom would not boot. When I converted all filesystems back to ext4 all problems would disappear. Mount would show correctly and roms would flash ok. Any ideas?
[Samsung Galaxy Nexus] E66666666:
I reformatted my phone to f2fs with TWRP, but pushing the ROM file made the phone go black. It won't boot anymore. I can't get into recovery because the volume buttons are broken.

I have a USB jig and ODIN mode works, but after restoring stock everything, the Nexus boot logo (not Google logo) just stays there forever and Android doesn't boot.

How do I reformat everything back to ext4 with odin?
[Samsung Galaxy Nexus] Qafix:
Greetings guys. My phone always gets super laggy anytime I put in big size files (be it one big file or an assortment of files) and while I was on ext4 I could always just use lagfix to cure the slowdown. Since I started using f2fs however, I can't use lagfix thus it leaves me with the lag problem. I thought when converted to f2fs the write ups would not be a problem (it was blazing fast at first), but like mentioned, I had to put back everything on my phone after converting and now my phone will not stop being laggy. Is there something similar to lagfix that I can do on f2fs? Any help would be appreciated.
[Samsung Galaxy Nexus] poo706:
I had the exact same behavior with big files on my nexus 7. I switched back to ext4 as a test and they completely went away. I won't be switching back. Curious, I'm always down to about 2-3 GB of free space on my N7 because it's just an 8GB model. Are you really low on space too?

[poo]