yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] Aronuser:
oh... then it was all useless LOL :p Cheers :highfive: Thanks

---------- Post added at 11:32 PM ---------- Previous post was at 11:16 PM ----------

Actually I've to say that since I updated AOSPA to Kitkat 4.4.3 and F2FS file system it's all super fast :cool::cool::cool: Awesome work F4k
[Galaxy S 4 Mini Android Development] kamikaze702k:
I'll try this f2fs some day

Sent from my GT-I9195 CarbonKat 4.4.2
[Galaxy S 4 Mini Android Development] Aronuser:
I saw that there is a new option to wipe preload in the twrp recovery, what is it good for and is it safe to wipe it?
[Galaxy S 4 Mini Android Development] fburgos:
Hi [MENTION=3261191]F4k[/MENTION]

do you think you can port carbon rom/recoveries to i9192

According to developer is

Source: http://xdaforums.com/showthread.php?t=2767844

thanks for your time
[Galaxy S 4 Mini Android Development] mielletseed:
[MENTION=3261191]F4k[/MENTION]: your TWRP recovery (the i9190 one) works perfectly on my i9192. The only thing is, I always have to edit the zip files to remove the device check since the revovery thinks, it was a i9190 instead of i9192. So could you please provide a third version with the device string "serranods" instead of "serrano3g"?

Thank you a lot!
[Galaxy S 4 Mini Android Development] F4k:
I'll take a look.

If recovery works without any other modifications, doesn't make sense to add a third zip, easy way is to remove device's check on updater-script, so anyone could use on a serrano3g/serranods
[Galaxy S 4 Mini Android Development] mielletseed:
I think, you misunderstood. It's not only the device check in YOUR ZIP-file with the recovery ...

Every single ZIP (e.g. CM11 for i9192) file has a device check in updater script. When I'm using your TWRP for i9190 the device "thinks" it was a i9190 (serrando3g) and denies to install the ROM for i9192 (serranods). So I always have to edit my zip files (every single nightly build) to install them.

So I think inside the recovery somewhere ist the device string for "this device" stored.

A little bit more clear now?
[Galaxy S 4 Mini Android Development] F4k:
Yes, you're right, serrano3g variant uses a default.prop accordingly with this device, so it's normal that other installation script thinks that is a serrano3g device 'cause is checking default.prop, I'll see if can make a serranods variant.
[Galaxy S 4 Mini Android Development] F4k:
Updated Philz Touch F2FS to 6.47.6

Also, I added support for S4 Mini Duos (

GT-I9192

,

serranodsub

), so please if someone can confirm if it works correctly.

Regards!
[Galaxy S 4 Mini Android Development] fburgos:
tried twrp for i9192, working fine i think the file system conversion its ok for data and cache

change those lines in the carbon build for i9192 but fail to install then my /system is ext4
[Galaxy S 4 Mini Android Development] mielletseed:
TWRP works for me! Thank you a lot!
[Galaxy S 4 Mini Android Development] ssceddie:
Is Only CarbonROM 4.4.3 support F2FS oder all (include the new CarbonROM 4.4.4) ?
[Galaxy S 4 Mini Android Development] F4k:
Latest version it has support too, but if you want /system formatted as F2FS, you'll need to edit updater-script like I said in OP.

Otherwise, you'll get /system partition formatted as Ext4
[Galaxy S 4 Mini Android Development] ssceddie:
Sorry, but where i can find the "updater-script" in the CARBON-KK-UNOFFICIAL-20140620-1357-serranoltexx.zip ?

or where i have to edit that???
[Galaxy S 4 Mini Android Development] F4k:
Here you have, you need to extract this zip file, and replace updater-script on CarbonROM's zip file with this one.

You'll find updater-script under folder META-INF/com/google/android/

Good luck! :)
[Galaxy S 4 Mini Android Development] aguaz:
TWRP_2.7.1.0_serranodsub_F2FS on GT-i9192:

- No adb USB debugging!?

- No /data encryption support!?

Both work ootb in OliverG96's TeamWin Recovery 2.7.1.0 for GT-I9195
[Galaxy S 4 Mini Android Development] F4k:
1- Works fine for me

2- No ATM
[Galaxy S 4 Mini Android Development] GNUDroid:
Hi, I hope I did not missed such an post

Can someone is more in contact to CM Dev's tell me about their planings to implement F2FS in heir stock CM kernel? Any information if this will happen by time? Anyone who knows the planing of the CM team?

Background: I really want to try f2fs, but I'm struggling because in case of rom problems I also want to be able to use the stock CM kernel. And always full wipe/reformat is not an solution for me. Hopefully they add support soon (not as default but adding the f2fs as a kernel module, if the kernel finds an f2fs formated internal memory whilst booting).
[Galaxy S 4 Mini Android Development] impactor:
I am trying to run latest C-Rom on full F2FS phone (including external sd). I modified updated-script and installation went fine. However, I have no access to external sdcard.

Even when I try to mount it manually, I get:

# mount /dev/block/vold/179\:33 /storage/sdcard1/
mount: bad address '/dev/block/vold/179'

The first post of this thread says

But what does it even mean? I was unable to google anything on this subject, nor find anything on xda forums.
[Galaxy S 4 Mini Android Development] F4k:
It mean what it mean, you'll no able to use external sdcard formatted as F2FS on ROMs that doesn't have F2FS support on vold binary.

AFAIK the only ROM that have this support is my CarbonROM builds, because I added this support.
[Galaxy S 4 Mini Android Development] impactor:
I see. What is the latest version of the CarbonROM you added the support to? And if it's not 4.4.3, then where can it be downloaded?
[Galaxy S 4 Mini Android Development] Phenom2122:
http://xdaforums.com/showthread.php?t=2642488

I've been meaning to report this for a while now but every time I notice it, by the time I have finished what I'm doing I've forgotten about it. I am unable to format /preload, this is the message I get:

"E:format volume: mkfs.f2fs failed on /dev/block/platform/msm-sdcc.1/by-name/hidden"

The same goes for ext4. Does preload even still exist in the latest Android?
[Galaxy S 4 Mini Android Development] jake3317:
[MENTION=3261191]F4k[/MENTION], I successfully used your TWRP to turn my i9195 into an all F2FS file system phone and installed the CC0613 version on it. This was working great. I then made a full backup before dirty flashing CC0628 over top of it (replaced the updater-script as described). This installed fine as well, except that WiFi wasn't working. Therefore I went back to recovery and restored my backup from before. Unfortunately I miss my files from my internal SD-card. All apps are there, the app content (like SMS and call logs, wifi and bluetooth are restored, but my whole download folder and DCIM folder with pictures is gone. Have I missed something? Did I forget to backup some data? I believe I checked all boxes in the backup window in the recovery mode.
[Galaxy S 4 Mini Android Development] F4k:
TWRP backup only /data, not internal sdcard, probably it was formatted when you restored your backup, it happened to me also and I don't know if is normal.

That is why I recommend doing a backup when converting to f2fs, I think that Philz Touch doesn't format internal sdcard at least that you do it.
[Galaxy S 4 Mini Android Development] jake3317:
Thanks for your quick reply. I used the 0613 version for 2 weeks fine. The issue was with the restore. I understand now that data and internal sdcard are not the same. Any chance to recover from a formatted internal sd-card?
[Galaxy S 4 Mini Android Development] F4k:
I doubt it, but you can try with some data recovery tool.
[Galaxy S 4 Mini Android Development] jake3317:
I think I know what caused my internal sd card to be formatted accidentally during a restore:

I was on an 'all F2FS' system, backed up all 'check boxes' in TWRP and restored that one after a failure with my latest ROM.

During the 'restore' I already saw the commands coming by 'formatting with ext4', which was strange. After booting the ROM again, my initial issues were gone, luckily, but I discovered that all my personal data was gone.

Booting to recovery again, I discovered that the checkmarks "Force data and cache wipe functions to use F2FS" and "Include system partition" were not checked anymore.

After placing this checkmarks again, the same backup restored back to F2FS without issues. I put some files in my download folder and restored the system again. This time my personal files in 'download' remained where they were. I think it went wrong when the data partition was formatted to ext4, TWRP wasn't able to skip the /media folders as it would do when the old and new file system were identical.

Tip for next time: Check in recovery what filetype your backup is and also in 'settings' if the correct filesystem is used for formatting. and OK, OK, make a backup of personal data somewhere else (I had done that 2 weeks ago when I went to the F2FS file system. Unfortunately I had cut-pasted my data back. Next time it will be copy-paste)
[Galaxy S 4 Mini Android Development] Phenom2122:
Philz doesn't go near the internal SD unless you specifically choose to format it. In fact I don't think it formats anything when it restores but on that I may be wrong.

I really don't think that it is normal behavior to format it on restore, that is where all it's settings are stored and in my case where I keep my backups. That could only cause trouble.
[Galaxy S 4 Mini Android Development] impactor:
Is it possible to add F2FS support (including external SD card) to a 4.3.1 rom? If so, is it the same process as adding it to a KitKat rom?
[Galaxy S 4 Mini Android Development] Phenom2122:
The Rom itself has to also support F2fs so unless it is a modified 4.3.1 Rom then the answer is no, unfortunately. Plus, not all Roms that support F2fs support it for the external SD as well. I believe that Carbon is the only one that does at the moment.
[Galaxy S 4 Mini Android Development] impactor:
I know that. My question was "how to modify a ROM to add support for it".
[Galaxy S 4 Mini Android Development] johny.mnemonic:
[MENTION=3261191]F4k[/MENTION] Would it be possible to update Philz recovery to latest version?

It has some fixes for working with F2FS and maybe you can also enable exFAT.
[Galaxy S 4 Mini Android Development] F4k:
I'll update very soon.
[Galaxy S 4 Mini Android Development] alexax66:
Hello.

Thank you very much for your excellent work.

I'm using Cyanogen since the very first build of [MENTION=5368296]sekil[/MENTION].

Your last CM11 builds are very stable and faster.

Now I want to make the transfer cm11 on f2fs. I have all for it.

I have compiled the CM11 kernel for i9192 with support f2fs and plan to make the ROM using your ready builds.

I want to spread the my modified CM11 builds for the public with reference on the your threads.

I hope that you do not take me against this.

Pleas make Philz recovery with exFAT support!
[Galaxy S 4 Mini Android Development] F4k:
You mean internal sdcard? I think that you can not, on Philz's recovery you can achieve this, because it have an option to backup data/media folder and TWRP doesn't have this option.
[Galaxy S 4 Mini Android Development] jukyO:
Ok. Thanks.
[Galaxy S 4 Mini Android Development] jukyO:
[MENTION=3261191]F4k[/MENTION]

What about

mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data")

When installing new version of ROM update ( CM 11)?

System and Data already converted to f2fs.

Should this be ignored or changed also to something else?
[Galaxy S 4 Mini Android Development] jukyO:
[MENTION=3261191]F4k[/MENTION]

Bump. Can you shed some light here?
[Galaxy S 4 Mini Android Development] F4k:
It's already explained on OP, check it!
[Galaxy S 4 Mini Android Development] jukyO:
Thanks, but nothing there on mounting '/data'.

For '/system' it is clear.

Asking, because in CM11 rom updater-script, there is above mentioned:

mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data")

Should it be changed to:

run_program("/sbin/busybox", "mount", "/data");

Thanks.
[Galaxy S 4 Mini Android Development] jukyO:
Confirming. Works a treat.
[Galaxy S 4 Mini Android Development] S3miniFin:
Any other links w/o some fuc*king downloader available for #2 links?!?
[Galaxy S 4 Mini Android Development] alexax66:
Hi!

I ported Philz Touch 6.58.7 for I919x family

What's new:

based on ClockworkMod v6.0.5.1

support Dalvik/ART wiping

support F2FS format for system, data and cache partitions

advansed F2FS formatting for system, data and cache partitions

automount sdcard1 in FAT/FAT32/exFAT format

Enjoy!

Link:https://s.basketbuild.com/devs/alexax66/CWM/
[Galaxy S 4 Mini Android Development] Tirofog:
I could never get adb in recovery to work with CWM based recoveries, plus booting a TWRP based recovery was always inconsistent. This one boots first time and has it all – adb, USB storage mount, F2FS etc. Many thanks for sharing!
[Galaxy S 4 Mini Android Development] tchavei:
Is it just me or the zips appear as invalid? I can't flash any of them. They don't even open in root Explorer although they have the correct size?

Regards

Tony

EDIT: dolphin browser's multithread download system was screwing the downloads... It's OK now

Sent from my GT-I9195 through Tapatalk
[Galaxy S 4 Mini Android Development] F4k:
New TWRP 2.8.1.0 F2FS builds online!

Thanks to [MENTION=5739341]thomson.aa[/MENTION] for the fix!
[Galaxy S 4 Mini Android Development] pakster67:
Seems that the brightness control doesn't work.

Anyway thanks.
[Galaxy S 4 Mini Android Development] F4k:
Me too, probably the fix that I'm using to make it work TWRP for our devices, breaks this brightness control feature.
[Galaxy S 4 Mini Android Development] pakster67:
A little sorry, but it is not fatal ;)
[Galaxy S 4 Mini Android Development] hawaianas:
Very strange: I installed the new release without any problem but I can't decrypt the data partition in recovery mode. Anybody else is experiencing this phone's behaviour? Or, on the contrary, anybody is able to decrypt the data partition in recovery mode?

Thanks in advance
[Galaxy S 4 Mini Android Development] ghuertasw:
Hi there! I updated TWRP to the latest, but I can't make any Backups.... :(

Is there any way to get a log? Each time I try, it just restarts the Recovery!
[Galaxy S 4 Mini Android Development] pakster67:
The same here! :(
[Galaxy S 4 Mini Android Development] F4k:
I've just tested a backup to ExtSD, no issues here.
[Galaxy S 4 Mini Android Development] ghuertasw:
Guess I'll reinstall and try again.... :thumbup:

Ok. After reinstall, it's working again! :D

Enviado desde mi super i9190 usando F4K's Rom & kernel!
[Galaxy S 4 Mini Android Development] pakster67:
I've just reinstalled TWRP - earned :confused: :)

And a little question - is it possible to fix the issue with brightness control?
[Galaxy S 4 Mini Android Development] mielletseed:
[MENTION=3261191]F4k[/MENTION]: In your latest TWRP version 2.8.1.0 for i9192 making a backup doesn't work to me. Also the file system check seems not to work. Went back to your 2.7.1.0 and there it works.
[Galaxy S 4 Mini Android Development] F4k:
Try to copy recovery.log and see why backup has failed.
[Galaxy S 4 Mini Android Development] mielletseed:
I installed 2.8.1.0 again to pull a log - but what should I say - now the backup works. Strange.

Cool is the new counter for files and size! Thank you!
[Galaxy S 4 Mini Android Development] ghuertasw:
Jaja same thing happened to me! Couldn't replicate the error... :confused:

Enviado desde mi super i9190 usando F4K's Rom & kernel!
[Galaxy S 4 Mini Android Development] mielletseed:
[MENTION=3261191]F4k[/MENTION]: In both recoveries (2.7.1.0 and 2.8.1.0) i have no adb debug but adb sideload is working. There is nothing dedected in my pc while in the recovery. Any hints to get the adb debug working?
[Galaxy S 4 Mini Android Development] ozi5783:
Hi! can someone guide me in modifying updater-script in F4k's CM12? i want to use f2fs in /system partition, but i cannot find

format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");

in updater-script. and there are 3

mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");

codes. should i replace them all?

thanks
[Galaxy S 4 Mini Android Development] F4k:
I suppose that you're using a recovery like my TWRP with F2FS support.

You'll need to format manually partitions that you want to be on F2FS, and change:

mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");

to:

run_program("/sbin/busybox", "mount", "/system");

change:

mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");

to:

run_program("/sbin/busybox", "mount", "/data");
[Galaxy S 4 Mini Android Development] ozi5783:
thanks for the answer. i will try tomorrow and give you feedback.

i don't want to be a pain in the a**. i come from s3 mini, and there we have a rom built with aroma, and so, we could choose things from the installer.

i am not yet used to modify things in rom.zip, but i like cm and i will learn anything it takes to flash this latest rom, official or unofficial.
[Galaxy S 4 Mini Android Development] alexax66:
I made new port of PhilzTouch 6.59.0 with f2fs support

Link: https://s.basketbuild.com/devs/alexax66/CWM

Bug: brightness control doesn't work :(
[Galaxy S 4 Mini Android Development] Ahmedivx:
Thanks a lot for this great mod of TWRP, it has been recently updated to v2.8.5.0 , is there any chances of updating to the latest version for all variants, thanks a lot.
[Galaxy S 4 Mini Android Development] F4k:
Indeed
[Galaxy S 4 Mini Android Development] patar1991:
excuse me sr I have 1 question ... can i use dualboot and this feature or it cant be possible im a noob using this features
[Galaxy S 4 Mini Android Development] F4k:
I've pushed new builds of TWRP, I mean version 2.8.6.0 (lp-5.1) with F2FS support.

serrano3gxx (I9190)

serranoltexx (I9195)

Odin/Heimdall .img file or flashable .zip file :)
[Galaxy S 4 Mini Android Development] Draylin:
Thanks F4k! :)

I only faced one small issue. It seems like the brightness adjustment doesn´t work.
[Galaxy S 4 Mini Android Development] F4k:
No, it doesn't.
[Galaxy S 4 Mini Android Development] 96DANGER96:
Why I can't edit the updater-script on you CM12.1? It is the first time I try to format F2fs
[Galaxy S 4 Mini Android Development] F4k:
Added S4 Mini Duos variant

serranodsxx (I9192)
[Galaxy S 4 Mini Android Development] FastGas:
your recovery works well :good:
[Galaxy S 4 Mini Android Development] p@to:
hi

and thanks

Is it this same procedure?

For TWRP

1.1) Go to Settings and select "Force data and cache wipe functions to use F2FS" and if you want F2FS support on /System partition, select "Include system partition"

1.2) Now go to Wipe menu and select Format Data and type "yes" (Warning this will format Data partition and your Internal Storage, so please don't forget to make a backup of your personal data)

1.3) Optional, select Advanced Wipe menu and check System and Cache partitions to convert to F2FS respectively.

thanks again
[Galaxy S 4 Mini Android Development] p@to:
Any help to use twrp f2fs option?
[Galaxy S 4 Mini Android Development] lars85destroyer:
Can I use this recovery even if I don't use F2FS on my partitions ?
[Galaxy S 4 Mini Android Development] axman79:
Yes...u can
[Galaxy S 4 Mini Android Development] AndreAkaNick:
Cant find "Force data and cache wipe functions to use F2FS" in settings.

Any help?

Using TWRP 2.8.6.0 I9195
[Galaxy S 4 Mini Android Development] thallyswb:
I'm trying to modify the updater-script in CM 12.1

To try to activate f2fs the partition on /system.

Always comes back to ext4, I tried TWRP 2.8.1.0, and TWRP 2.8.6.0 unsuccessfully, always back = /

Already modified as f4k says this post: http://xdaforums.com/showthread.php?t=2776430&page=11

I think to be the CM12 code did not work in CM12.1, always comes back to ext4.

The script code is this:

Any solution? Thank you!
[Galaxy S 4 Mini Android Development] jukyO:
You did it wrong. Two pages back f4k explained,:

http://xdaforums.com/showthread.php?p=57898553
[Galaxy S 4 Mini Android Development] martin.eu:
Hi, also cant find Force to use F2FS option in settings menu... any solution available ?
[Galaxy S 4 Mini Android Development] arsm74:
TWRP 2.8.7.0

[MENTION=3261191]F4k[/MENTION], i believe the TWRP code was recently upgraded to 2.8.7.0. are there any plans to upgrade your f2fs port as well?

thanks again for all your work on this.
[Galaxy S 4 Mini Android Development] arsm74:
me too....
[Galaxy S 4 Mini Android Development] yaroszek:
I have this option first i installed 2.8.1.0 then reboot recovery and install 2.8.6.0. But i cant backup my system with any wersion of this twrp. In normal (without f2fs) backup works fine.
[Galaxy S 4 Mini Android Development] interstellar22:
great tool to use , i use it on both of my devices, but none of them are really supported by twrp , as not on the website :)

Could you maybe compile the newer version 2.8.7.0 ? I would be willing to test :)

Thanks in advance and keep up the good work & tell us how we can help you :)

All the best

---------- Post added at 02:34 PM ---------- Previous post was at 02:33 PM ----------

just go to wipe /advanced and format your partition to f2fs, its really simple, it is there trust me :)
[Galaxy S 4 Mini Android Development] hollandais:
I use twrp 2.8.7.0 on my I9195, and it seems well.

http://xdaforums.com/showthread.php?t=2678420

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Android Development] ozi5783:
i have been trying to install CM12.1 official nightly with f2fs on /system all this morning.

here is the updater.script that i used:

assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" || getprop("ro.product.device") == "serranoltebmc" || getprop("ro.build.product") == "serranoltebmc" || getprop("ro.product.device") == "serranoltektt" || getprop("ro.build.product") == "serranoltektt" || getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" || abort("This package is for device: serranolte,serranoltebmc,serranoltektt,serranoltexx; this device is " + getprop("ro.product.device") + "."););

ifelse(is_mounted("/system"), unmount("/system"));

package_extract_dir("install", "/tmp/install");

set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);

set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);run_program("/sbin/busybox", "mount", "/system");

run_program("/tmp/install/bin/backuptool.sh", "backup");

unmount("/system");

if is_mounted("/data") then

package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");

run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");

else

run_program("/sbin/busybox", "mount", "/data");

package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");

run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");

unmount("/data");

endif;

show_progress(0.750000, 0);

ui_print("Patching system image unconditionally...");

block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");

show_progress(0.020000, 10);run_program("/sbin/busybox", "mount", "/system");

run_program("/tmp/install/bin/backuptool.sh", "restore");

unmount("/system");

show_progress(0.050000, 5);

package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");

show_progress(0.200000, 10);

the fylesystem always changes to ext4 with both F4k's and ne0zone75's recovery. i can't find what is wrong, and i read all recovery threads.

i used this method and it worked, but i guess i cannot update the old fashion quick method.

any suggestions?