yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] blackbird5308:
It works!

Updated today, results, it works, but the modrd.sh is the old version, as i was pointing out on the thread in dev section some days ago. You should update the script to mod the ramdisk, as mods are required for it to boot.

EDIT: i forgot, thanks a lot for building it! :)

I repacked it with the new files, and this works for me without any problem :D

I link it here if someone needs it:

https://drive.google.com/file/d/0B2jwGs_PLNsOaGw2eWhLUjEwcTA/edit?usp=sharing
[Nexus 4 General] jolinnard:
Thanks for the advise. I will update modrd.sh later :)

Edit: zips updated in my server too. Thanks again. Can you post the source of that files? I can't find them in Franco github...

---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------

All kernels I build that has "auto" in its name can be flashed in both situations (ext4 and f2fs).
[Nexus 4 General] InvalidCast:
system:eek:K, cache:eek:K, data:KO

hi

i followed instructions and manage to have a F2FS slimkat and a F2FS franco kernel, on a F2FS system.

i also managed to format cache in F2FS

BUT, i cannot manage to format data in F2FS

1) i tried "format data" menu, which says that it formats using mkfs.f2fs

while in twrp, in terminal, i can see that /dev/block/mmcblk0p23 on /data is F2FS (which is similar to system and cache, that are well F2FS formatted)

2) i tried to modify updater-script of formatpartitions.zip, to add a command for data.

i tried:

a) run_program("/sbin/mkfs.f2fs", "/dev/block/mmcblk0p23");

b) run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/data");

c) run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/userdata");

3) i tried to directly run the above commands in twrp terminal, for ex:

/sbin/mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata

i also tried many combinations of the 3 above point, with "reboot to recovery" or not between them.

if i remember well, commands on "/dev/block/platform/msm_sdcc.1/by-name/data" did not worked well but "/dev/block/platform/msm_sdcc.1/by-name/userdata" did work.

also, "format data" did not work the first time: data was not formatted at all, all files were still here.

and a time, don't know why, it formatted, but in ext4

when i go to "disk info" app or terminal app (not in twrp) after reboot, /data appears as ext4
[Nexus 4 General] Rohit02:
Can someone tell me the procedure to flash the cm f2fs rom.. i

am on aosp and wen i flash cmf2fs based rom it fails.. the

detailed procedure please.. Asap.. please..TIA.
[Nexus 4 General] jolinnard:
Try to do the following:

adb shell

$ umount /data

$ mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata

Reboot to recovery again.

This should be enough. Then, check what format it has:

$ mount /data

$ grep /data /etc/mtab

You should see this:

/dev/block/mmcblk0p23 /data f2fs rw,relatime,background_gc=on,user_xattr,acl,errors=continue,active_logs=6 0 0

In this moment, push your ROM to your new /data (/sdcard should be emulated too, but if not push it to /data directly), gapps and kernel. If you use Slimkat posted in OP should work fine. Then you can change the kernel to my Franco, for instance.
[Nexus 4 General] InvalidCast:
just to say i saw this solution.

go to bed now, but will try tomorrow.

i suspected that data mounted was a problem (although i unmounted it from twrp before try to format it)

tomorrow will post the result.

thanks

edit:

adb shell, is from adb from computer or is it a command to execute in twrp terminal? (that's the noob question :) )
[Nexus 4 General] gharrrrrr:
From computer terminal. Make sure you have adb properly set up on your computer.

Sent from my Hammerhead using my T.A.R.D.I.S.
[Nexus 4 General] CallMeAldy:
Manually edit the updater script

Don't replace the boot.img

Flash the rom and flash any jolinnard's CM kernel

Reboot :)
[Nexus 4 General] InvalidCast:
i tried what you told. it seemed to work:

grep /data /etc/mtab

/dev/block/mmcblk0p23 /data f2fs rw,relatime,background_gc=on,user_xattr,acl,err

ors=continue,active_logs=6 0 0

this is when in recovery, just after the the mkfs.f2fs command and the recovery reboot.

BUT as soon as i boot, this is what i get (not from grep /data /etc/mtab, i cannot get it when booted. so from mount):

/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no

dev,noatime,nomblk_io_submit,nobarrier,noauto_da_alloc,errors=panic,data=ordered

0 0

and when in recovery again (after normal reboot):

grep /data /etc/mtab

/dev/block/mmcblk0p23 /data ext4 rw,seclabel,relatime,data=ordered 0 0

i must say that i don't want to reflash rom or kernel.

- i have a compatible F2FS ROM (made with this http://xdaforums.com/nexus-4/development/script-convert-rom-to-f2fs-t2731652)

- i now have your hellsgod kernel, but before, i tried with your franco kernel.

so, i execute all the commands with already a compatible rom and kernel (which might be needed to get mkfs.f2fs?)

it seems that when i do normal reboot, data is reformatted in ext4, no matter what i do.....

is there something i can check to see if a script, somewhere, do these kind of things?
[Nexus 4 General] fr3quency:
I can confirm it works with jolinnard's ak modified kernel. Afterwards, I flashed latest official ak kernel and it booted fine.
[Nexus 4 General] jolinnard:
This happens because you don't patch fstab properly. What kernel exactly do you flash? If you flash some of my auto kernels, maybe, it has a bug, because all of them should detect your f2fs partitions and correct the fstab.

And you can flash the same ROM you have right now. Just convert it if nobody posted a patched version.

To explain a little bit what is going on, when you read that a kernel is "F2FS compatible" only describes that this kernel is capable to mount F2FS filesystems. It doesn't mean that magically you can mount your internal partitions formated in f2fs. That should be specified in /fstab.mako file, which comes with boot image (or the boot partition). This is why I repack and patch zips from kernel developers ;)
[Nexus 4 General] tnp9008:
I just got my N4 setup with All-F2FS. Which of the F2FS kernels has USB-OTG support? I plan on using Hellscore when I get my phone setup but I need OTG to restore my Titanium Backup from my USB drive.

Sent from my MacBook Pro using Chrome

Phone: Nexus 4 + All-F2FS + Purity + Hellscore b46-t4
[Nexus 4 General] InvalidCast:
i tried with both franco.Kernel-nightly-r207-F2FS-auto.zip and JolieInHell-b46-t4-F2FS-auto.zip, both found at http://mirror.lnx.im/android

i think they are from you (at least the hell one)

i'm ready to test whatever you want :)

another kernel? do you need some info?

---------- Post added at 06:53 AM ---------- Previous post was at 06:02 AM ----------

when i flash, i always flash all at once (rom + custom kernel)

so, with what you said, i tried to flash only the rom, format data...... and yes!!!!

so, the fstab in the rom kernel must be good, whereas there seems to be a problem with the "auto" kernels.

if you need some beta tester, i'm here :)

PS: i have flashed your franco auto kernel AFTER rebooting and seeing it was good f2fs and now it works....

so in my case, what worked (already having system and cache in f2fs)

- flash f2fs rom

- format data

- reboot recovery (not sure needed here)

- reboot system

- check that data is f2fs

- reboot recovery

- flash f2fs custom kernel

- reboot system

it seems that:

- something is done at first system boot, that is needed for auto kernel to know it has to mount data as f2fs.

- flashing custom kernel right after rom, without system rebooting, prevent that thing to be done

at last, with your indications, i manage to do it :)

thanks
[Nexus 4 General] Rohit02:
To report.. Your Hellscore cm based gave me bootloop on cm based Crdroid rom.. Then I just flashed the rom n gapps n rebooted-all was good.. Aosp hells working good with Mahdi..
[Nexus 4 General] jolinnard:
Please, try this. If it doesn't work, maybe something in kernel is wrong.

---------- Post added at 10:32 AM ---------- Previous post was at 10:23 AM ----------

Yes, this is my server. If you flash Franco again, can you execute after this command?

cat /tmp/fstab.mako

or you can pull that file to your machine with adb or similar tools.

This is a copy of the patched partition table. You should see how the kernel will mount your partitions.
[Nexus 4 General] InvalidCast:
so, even, if now it's working, here is the result (that is now off course good :) )

cat /tmp/fstab.mako

# Android fstab file.

#<src> <mnt_point> <type> <mnt_flags a

nd options> <fs_mgr_flags>

# The filesystem that contains the filesystem checker binary (typically /system)

cannot

# specify MF_CHECK, and must come before any filesystems that do specify MF_CHEC

K

/dev/block/platform/msm_sdcc.1/by-name/system /system f2fs ro,n

oatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait

/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noat

ime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait,check

/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noat

ime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait,check

,encryptable=/dev/block/platform/msm_sdcc.1/by-name/metadata

/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosu

id,nodev,barrier=1,data=ordered,nodelalloc wait

/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,u

id=1000,gid=1000,dmask=227,fmask=337 wait

/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defa

ults defaults

/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defa

ults defaults

/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defa

ults defaults

/dev/block/platform/msm_sdcc.1/by-name/modem /radio emmc defa

ults defaults

/dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl1 emmc defa

ults defaults

/dev/block/platform/msm_sdcc.1/by-name/sbl2 /sbl2 emmc defa

ults defaults

/dev/block/platform/msm_sdcc.1/by-name/sbl3 /sbl3 emmc defa

ults defaults

/dev/block/platform/msm_sdcc.1/by-name/tz /tz emmc defa

ults defaults

/dev/block/platform/msm_sdcc.1/by-name/rpm /rpm emmc defa

ults defaults

/dev/block/platform/msm_sdcc.1/by-name/aboot /aboot emmc defa

ults defaults
[Nexus 4 General] ljames_21:
AK Kernel FCing

Hi, I get FCing on location service, android process, google play service, wifi authentication problem and etc after I flashed AK kernels. Everything works fine with hellscore and hellsdoctor kernels. Anyone having same issue? Or, Did I miss anything?
[Nexus 4 General] smile_hh:
I brush into the compatible with f2fs Crom 6.2 boot error process com.android.phone has stopped... How to do?
[Nexus 4 General] zorginho:
[MENTION=2002216]jolinnard[/MENTION] A f2fs fix from barome

https://github.com/barome/kernel_msm/commit/a4f90f00cecc3b668af9cf6c1795d0d1fb0b2426

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 General] shubu000:
What does the bug fix mean?
[Nexus 4 General] zorginho:
From github:

"f2fs: fix wrong statistics of inline data"

Not so well explained

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 General] jolinnard:
All my builds are refreshed. Look for "20140518" in the name.

I also build an AK kernel with that little fix. I added in the zip "Jolie". Actually, I'm running this without issues.
[Nexus 4 General] blackbird5308:
Oh, you built CM franco too <3 :laugh:
[Nexus 4 General] jolinnard:
Please, let me know if it works on your CM... I think I forgot to apply CM patch :silly:

Edit: Yep. I'm uploading right now again.
[Nexus 4 General] blackbird5308:
In fact, i had a little WTF impact on the first build :p now everything's good, thanks :D
[Nexus 4 General] Rohit02:
Yes I had downloaded from the very same link and it gave me bootloop.
[Nexus 4 General] shubu000:
i tried jolinard's franco, but just about every app is force closing..

anyone else seen that? i'm on hellsdoctor right now

rom's purity, all f2fs
[Nexus 4 General] jolinnard:
I never experience anything like this. It sounds like /data couldn't be written. I will try to test it later.

---------- Post added at 12:09 AM ---------- Previous post was at 12:04 AM ----------

Ok... So I'm lost too...
[Nexus 4 General] sean222:
It's not the kernel :) Jolinard's Franco r207 is running amazing for me :D

You need to wipe EVERYTHING and start the F2FS formatting all over...definitely not the kernel ;)
[Nexus 4 General] shubu000:
mmm strange, i trust jolinard's kernels, been using them for a while :D

but yeah somehow only hellsdoctor work for me now, and i use the one straight from barome, would that have been a problem?
[Nexus 4 General] jolinnard:
It wouldn't. I don't build HellsDoctor, only add my patch to the zip. Franco, Semaphore, Hellsgod and Matrix are built from source and added F2FS modules and my script in the zip files.

So use barome's zip if you patch your boot.img before (using a patched ROM or something).

BTW I'm very comfortable with AK. Last versions are amazing. I have some screen freezes with Franco (something strange, when I was moving out of my company building), but never with AK... I can't find why.
[Nexus 4 General] jckwht:
I have the same problem
[Nexus 4 General] WiwiPouPou:
Error sorry

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 General] snak3ater:
Any chance of getting Trinity kernel F2FS compatible?...It's the only thing which is stopping me from jumping onto F2FS
[Nexus 4 General] st1llal1ve:
Is it possible to convert Liquid Smooth rom to F2FS ?

I just tried this script and got working rom, but my colors replaced randomly. Bootanimation not working (bad colors) Please help!
[Nexus 4 General] qu3becker:
I don't know much about Liquid Smooth but this seems to be the case of a wrong kernel is installed. Since CM uses Quallcomm's caf drivers instead of open source AOSP's, when flashing a wrong kernel, the colours go wonky. You'll have to flash another kernel with caf or AOSP compatibility depending on the ROM's base. You'll have to try again with the other type of kernel.
[Nexus 4 General] jolinnard:
Hi my friend! Please, try this. Hope it works fine.
[Nexus 4 General] jmtjr278:
[MENTION=2002216]jolinnard[/MENTION] Franco 208 just came out. Any chance you could make one that is f2fs for the community at large? Using your version of 207 with great results for the last week.
[Nexus 4 General] sean222:
+1 :)
[Nexus 4 General] jolinnard:
Uploading right now ;)

Thanks for the advice
[Nexus 4 General] joefso:
Hi when flashing the 208 CM f2fs version the screen colors are all messed up and during boot time the whole screen is scrambled , reverting back to 207 cm f2fs and everything is fine..

thanks for the awesome work!
[Nexus 4 General] gharrrrrr:
Where did you find this 208 cm f2fs Franco at?
[Nexus 4 General] joefso:
http://mirror.lnx.im/android/mako/
[Nexus 4 General] jolinnard:
Sorry, fixed. Download it again.
[Nexus 4 General] joefso:
Works jolinnard
[Nexus 4 General] blackbird5308:
Always confusing CM and non-CM, huh? :P

No, really, thanks again for this builds, working good here :)
[Nexus 4 General] jolinnard:
Yeah, so many kernels... Franco is the only one I build and patch manually, without scripts. Maybe I should do one next time...
[Nexus 4 General] okanb3:
I just wanna ask little question, i want to go back to ext4 on my /system partition. I mean only i want only my /data partition stays at F2FS. I'm on full F2FS now. What must i do?
[Nexus 4 General] jolinnard:
Flash your original ROM+GAPPS first, that should format your /system in ext4. Then use one of my auto kernels. Should work.
[Nexus 4 General] barome:
Godzillandroid ???? Maybe you must say El Liberator and Barome
[Nexus 4 General] jimyiak:
But which recovery should we use if we want to format our system to ext4?the one with the red button formats system and cache to f2fs..

sent by neXus 4 kitkat-ed ?
[Nexus 4 General] jolinnard:
Keep F2FS recovery, and just flash your ROM. Scripts inside the ROM zip should format /system in ext4. After you need one of my auto kernels.
[Nexus 4 General] jimyiak:
Thanks..only auto kernels after?not for example the moob kernel which is f2fs compatible?thanks anyway..

sent by neXus 4 kitkat-ed ?
[Nexus 4 General] jolinnard:
My auto kernels detect the format of your partitions and patch the kernel partition table with that information. If you don't do this, it would be impossible to boot. When you see "f2fs compatible" kernels, only means that they are capable to mount a partition formated in f2fs, but it doesn't mean that they patch fstab.
[Nexus 4 General] jimyiak:
The auto kernels are only those on the psx/kernels folder?or there are somewhere else too?

sent by neXus 4 kitkat-ed ��

ok i'm on pc now and i see your signature..thanks!!
[Nexus 4 General] ashishv:
Jollinard i flashed velocity ext4 and your f2fs auto kernel over it,but now the rom.doesnt boot. I tried clean.install and tried to install f2fs rom again,but it didnt boot.what should i do as this is my only phone.
[Nexus 4 General] Rohit02:
[MENTION=2002216]jolinnard[/MENTION] : Can you make Slim's latest kernel compatible with F2FS. i know after converting any ROM to F2FS it has the slimkernel but I wanted the latest kernel. What say? A flashable zip would do. :good:
[Nexus 4 General] jimyiak:
And moob kernel is very good but not with your auto patch :):)

neXus⁴ running kitkat 4.4.2
[Nexus 4 General] NABENDU1:
+ Even I would love it [MENTION=2002216]Jollinard[/MENTION] !! And if possible a boot.img of the Kernel Zip too !! Even the Slim Kernel I use for the script is way too outdated !!
[Nexus 4 General] jolinnard:
OK, I will try ;)

I have found the code: https://github.com/SlimRoms/kernel_lge_mako and if I only need to add f2fs it would be easy. Which toolchain do you prefer? I usually use AK's 4.9.1...

Edit: it seems Slim team use linaro-4.8-13.06...
[Nexus 4 General] Rohit02:
Cool man.. :) The latest and better for battery backup and performance toolchain would do. Waiting... ;)
[Nexus 4 General] shubu000:
i am trying to revert all f2fs back to just ext4 for system and cache

i want to leave data as f2fs though,

anyone got an idea?

i tried to format the system and cache back to ext4 by flashing a "normal" ROM.

i wiped both these partition

and then i flashed jolienard's autof2fs but it just doesn't boot

anyone got any idea

thanks
[Nexus 4 General] zielonek430:
Hi!

I'm using currently PSX+Franco, "all f2fs". It is much faster than ext4, however I have a question. Having done everything according to the instruction in the first post I ended up with a working ROM, but userdata is not f2fs, but ext4 - is that OK or have I done sth wrong?
[Nexus 4 General] NABENDU1:
Here is the link !!

https://drive.google.com/file/d/0ByrfJAT1lgDFOUpCX294aExKSnM/edit?usp=sharing

Flash through recovery !! It will only erase ur data partition and probably solve ur problem !!
[Nexus 4 General] zielonek430:
Did not do anything. Neither did anything get erased nor did the file system change...
[Nexus 4 General] NABENDU1:
Okay something's not right with ur recovery !! Try redownloading the recovery and fastboot again !! Or else try multirom recovery( heard that too is f2fs compatible) and try again !!
[Nexus 4 General] zielonek430:
I reinstalled the recovery from the OP but still nothing changed... Do you have a working one?

Or maybe I should just perform a correct wipe from the TWRP wipe menu?

EDIT: I managed to get it working - just repeated the whole instruction without flashing kernel together with ROM - working all right :D
[Nexus 4 General] InvalidCast:
I had exactly the same problem - data still in ext4 whereas system and cache in f2fs.

and the problem was the same: flashing rom and kernel at the same time.

in fact, auto kernels (if you used them as i did) do not format data, they can handle ext4 and f2fs and detect which is used BUT do not change data format.

so you have to boot once without auto kernel, to format data in f2fs, then you can flash auto kernel.

maybe it should be said in OP, that at least a system (not recovery) boot is required before using auto kernel.
[Nexus 4 General] zorginho:
So We have to boot the first time with the included slim kernel in f2fs ROM? Or We have to flash a non auto kernel like hellsdoctor from barome?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 General] InvalidCast:
what worked in my case was to boot with the f2fs rom i chose (no matter which one) without flashing any other kernel.

the f2fs rom contains a "hard" f2fs kernel that will format your data in f2fs

so yes, boot without changing the kernel, after you flashed your f2fs rom
[Nexus 4 General] gharrrrrr:
May I ask which app that is you are using? Wanna check myself now too.
[Nexus 4 General] zielonek430:
It is "Partition Table" https://play.google.com/store/apps/details?id=com.cls.partition You have to go into advanced and check mmcblj0p21 to 23 (system, cache and data)
[Nexus 4 General] ashishv:
If u havent got a solution yet, you can get the f2fs rom rom to boot again by flashing format partitions followed by f2fs rom. :cool:
[Nexus 4 General] shubu000:
Does that wipe my data?

I haven't tried since
[Nexus 4 General] passlogin:
How do you mod a rom for f2fs?

I've modded the fstab, the updater-script.

And with the new boot img and a f2fs kernel my phone won't boot past the google screen. [MENTION=1737475]callmea[/MENTION]ny could you show how to mod the boot.img for validus for an example?
[Nexus 4 General] Rohit02:
Why dont you simplify your life mate. use the windows script by [MENTION=4668017]NABENDU1[/MENTION] and convert the ROM

Just a 4-5 clicks and you are done.

I believe Validus is AOSP so use that option and all is done. :)
[Nexus 4 General] jmtjr278:
https://play.google.com/store/apps/details?id=com.runnerway.converttof2fs

Works great for me. Cost is low and you can convert on the fly with a few touches.
[Nexus 4 General] ashishv:
Nope it doesnt wipe data.
[Nexus 4 General] jolinnard:
Finally, lastest Slim kernels uploaded to my server ;) The toolchain is AK-linaro (4.9.1-2014.05.20140518.CR83)

The SlimKernel-mako-F2FS-20140527-any-auto.zip has the anykernel method to patch your current boot.img (only tested in Slim ROM) and my auto script. SlimKernel-mako-F2FS-20140527.zip has a boot.img for those who request it ;)

Slim kernel builds this module drivers/scsi/scsi_wait_scan.ko so I added it too to the zips (it's better to have all updated).
[Nexus 4 General] jimyiak:
Can we use these kernels to convert a rom to f2fs with the script on windows?instead the one in the folder..i think the version with boot.img,right??

sent by neXus 4 kitkat-ed ?
[Nexus 4 General] jolinnard:
Yes, should work.

Edit: Please, download the zip again. There was a mistake with lastest boot.img. Now it should work :P
[Nexus 4 General] jimyiak:
New AK is up!!! ?

sent by neXus 4 kitkat-ed ?
[Nexus 4 General] HTCTOUCHPRO91:
New adreno drivers are out ;)

And new AK 268 is a bomb #)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 General] NABENDU1:
Thx a lot [MENTION=2002216]jolinnard[/MENTION] !! Im really indebted to you for giving me the boot.img !! Ill give this boot.img a shot in a while and if it boots fine this will be in the next version of the script !! And ya thx again !!

Edit the boot.img works just fine !! Ill add it to my script rightaway !!
[Nexus 4 General] joefso:
[MENTION=2002216]jolinnard[/MENTION]

what is so diffferent about the version of hellsgod you published ( called JolieInHell-b46-t4 ) other than f2fs compatible? I am testing atm
[Nexus 4 General] jolinnard:
Hi, I'm late. This was a personal choice to rename all kernels that have a modification (for instance f2fs module). I don't apply more modifications than f2fs in Jolieinhell... But, I keep its name for the moment.

[offtopic] In other hand, I had a red light of dead yesterday. Battery started warming and it turned off itself... After that I couldn't boot my N4. If I plug in the charge a red light is the only thing I got. After reading a lot of forums (like this thread in XDA), I decide to take off the back case and disconnect the battery. After that it seems to work! I flashed stock 4.4.3 and I want to wait a few days until back to flash custom ROMS/kernels.
[Nexus 4 General] mikaole:
Red light of death. Had it twice, but was lucky. Overnight charging always helped.