yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] johansenmo:
Yes, using the included boot.img. Nothing else modified besides the rm command line.
[Samsung Galaxy Nexus] poo706:
OP updated. The Linux tool is now Mac compatible. Thanks [MENTION=4111908]johansenmo[/MENTION].

[poo]
[Samsung Galaxy Nexus] poo706:
[MENTION=4145090]crazyeats[/MENTION], to answer your question posed in the dirtyv thread by mistake, which was:

I would imagine what you want is not what the vast majority of people want, so I'm hesitant to make the tool remove more than is necessary. However, if you give me a list of what you want removed, I can easily make you a custom version. Or you can add them to the script yourself, just modify the last line that starts with "7za d" (Windows), "zip -d" (Linux/Mac), or purge.sh (Android).

[poo]
[Samsung Galaxy Nexus] crazyeats:
I'm just looking to remove all gapps including play services. I'm not positive what all those apps are. I normally just don't flash gapps after me ROM. Currently on liquid and loving it. Haven't tried shiny since I switched to f2fs.
[Samsung Galaxy Nexus] poo706:
I say just stick with Liquid, it really is an excellent ROM. Plus, something always bothered me about Shiny. Its selling point is that it's practically stock, but so many people install Xposed and Gravitybox. Why not just go with a custom ROM that has all that and more built right in?

[poo]
[Samsung Galaxy Nexus] crazyeats:
Agreed. Liquid is hands down me favorite ROM. The plan was to install xposed on it and give up art for a bit but wasn't sure if I really wanted to. Pretty sure I could figure out how to add other apps to purge if I really wanted to. Thanks for ur great tool and hard work.
[Samsung Galaxy Nexus] aliesz:
Shiny 2014-07-07 version???!! where is it? the latest version of shiny is 2014-06-21!
[Samsung Galaxy Nexus] crazyeats:
07-07 shiny doesn't exist
[Samsung Galaxy Nexus] aliesz:
In Opening page of this thread, it has said in list of successfully converted ROMs.
[Samsung Galaxy Nexus] .B.0.W.:
https://www.dropbox.com/s/lrgx1djyhj3ckim/f2fsStockRom.zip

here you go
[Samsung Galaxy Nexus] aliesz:
It is not released by developer I think...:confused:
[Samsung Galaxy Nexus] poo706:
I didn't make that little note about shiny clear enough. I was referring to the 7/7 version of the converter tool.

[poo]
[Samsung Galaxy Nexus] .B.0.W.:
and? it's a working shiny rom that runs on f2fs.
[Samsung Galaxy Nexus] aliesz:
And it could not be as stable and trustful as the original one.
[Samsung Galaxy Nexus] poo706:
[MENTION=4111908]johansenmo[/MENTION], would you please run a quick test on your mac for me? Change the script in the 2014-07-11 Linux/Mac version to replace

FILE=`ls *.zip`

with

FILE=$(ls *.zip)

and see if it still detects the filename of the zip like it's supposed to. Thanks.

[poo]
[Samsung Galaxy Nexus] poo706:
Big news, at least for me, I don't have much going on in my life.

I was talking to Nautilus74 in the official LS maguro thread and he said that he has had no issues with any LS builds after 6/30 when using Fancy Kernel r51: http://xdaforums.com/galaxy-nexus/development/kernel-fancy-kernel-r50-t2115590

I wasn't aware of any other F2FS kernels besides dirtyv! So to those of you that had issues, I encourage you to give that a shot and report back. On a related topic, I'm making a toroplus LS right now with that ramdisk commit reverted. As long as it works like it should (I don't expect any issues), then I'll build for maguro and toro. Hopefully we'll be able to convert my unofficial LS's to f2fs and still be able to use dirtyv.

[poo]
[Samsung Galaxy Nexus] johansenmo:
[MENTION=3927368]poo706[/MENTION] confirmed working on MAC.

The included boot.img is SmittyV 06-28-2014.

Ensure no other zips are present in the converter folder.

Press ENTER to continue...
Archive: Slim-maguro-4.4.4.build.6.2-WEEKLY-5562.zip
signed by SignApk
inflating: META-INF/com/android/metadata
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: META-INF/com/android/otacert
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
deleting: boot.img
deleting: META-INF/com/android/metadata
deleting: META-INF/com/google/android/update-binary
deleting: META-INF/com/google/android/updater-script
deleting: META-INF/com/android/otacert
deleting: META-INF/MANIFEST.MF
deleting: META-INF/CERT.SF
deleting: META-INF/CERT.RSA
adding: boot.img (deflated 11%)
adding: META-INF/ (stored 0%)
adding: META-INF/CERT.RSA (deflated 33%)
adding: META-INF/CERT.SF (deflated 66%)
adding: META-INF/com/ (stored 0%)
adding: META-INF/com/android/ (stored 0%)
adding: META-INF/com/android/metadata (deflated 6%)
adding: META-INF/com/android/otacert (deflated 44%)
adding: META-INF/com/google/ (stored 0%)
adding: META-INF/com/google/android/ (stored 0%)
adding: META-INF/com/google/android/update-binary (deflated 36%)
adding: META-INF/com/google/android/updater-script (deflated 84%)
adding: META-INF/MANIFEST.MF (deflated 62%)

Process complete.
[Samsung Galaxy Nexus] poo706:
Wonderful, thanks!

[poo]
[Samsung Galaxy Nexus] mrgnex:
It looked awesome bt didn't work for me. I'm stuck at the Google splash screen after trying the windows gui version. I tried converting the latest vanir and it went from 199 mb to 195 mb so I thought it was converted right (using smittyv kernel) but now it wont boot..
[Samsung Galaxy Nexus] poo706:
Are you using smitty 6/28, the included boot.img? If so, try flashing fancy r51 (it's in the OP) or an older smitty from 6/15. Clearly 6/28 is not working out.

[poo]
[Samsung Galaxy Nexus] poo706:
What version of the tool are you using? I see Vanir is mounting data like slimkat does.

[poo]
[Samsung Galaxy Nexus] mrgnex:
Did the trick. I tried to keep up with this and the DirtyV thread but apparently missed something. Thanks!
[Samsung Galaxy Nexus] poo706:
[MENTION=5059314]mrgnex[/MENTION], what did you flash, Fancy?

[poo]
[Samsung Galaxy Nexus] mrgnex:
No I flashed the 15-6 SmittyV. Fancy wouldve worked probably but I wanted to try smitty again ;)
[Samsung Galaxy Nexus] Nautilus74:
But why do you insist on Smitty prefer? it leaves less than 700Mb free ...

DirtyV UR instead leaves almost 750MB free!
[Samsung Galaxy Nexus] mrgnex:
Newest features and more stability. I dont care much about ram..
[Samsung Galaxy Nexus] .B.0.W.:
you can make a swap partition if you want more ram, yet I'm not sure if you can still do it now.
[Samsung Galaxy Nexus] sergialess:
With Fancy r51 my phone is flying :cowboy:
[Samsung Galaxy Nexus] poo706:
New versions of all three tools, they now include Fancy r51 instead of the Smitty 6/28 that was causing a lot of problems. Also the OP now lists 3 alternative kernels. Let me know if I should add any others.

[poo]
[Samsung Galaxy Nexus] poo706:
So I made a unified liquidsmooth today.

http://xdaforums.com/showpost.php?p=54173260&postcount=11085

Then it occurred to me that I could modify my tool to take ext4 roms and make them unified as opposed to specifically f2fs. The plus side would be that we wouldn't need to worry about which f2fs boot.img to include with the tool, there wouldn't be one. The unified rom will select the appropriate fstab during installation and place it in the rom's stock kernel.

Anyone think it's worth the effort?

[poo]
[Samsung Galaxy Nexus] Nautilus74:
I'm trying your last Liquid unofficial with the new final Fancy52 ....

everything seems to work perfectly! ...

you can insert Fancy52 into your tool ....

Changelog:

r51 >> r52

fsync updates from later kernel revisions

defconfig: enable CONFIG_DHD_USE_SCHED_SCAN (hopefully helps with wifi reconnection issue)

add self-compiled stripped busybox with f2fs support

re-add rom-independent init.d support

execute init.d through busybox's run-parts instead of sysinit (which is not available in every ROM , e.g. shiny; fixes root issues reported by some users)

fix /system mounting to ro with f2fs fstab

increase sched_rt_runtime_us marginally (~1% more realtime cpu usage granted for parent cpuctl group; likely not noticable?!)

dont renice flush-daemon(s), they're already at +20 by default
[Samsung Galaxy Nexus] poo706:
I'll keep that in mind, thanks!

[poo]
[Samsung Galaxy Nexus] warlock9_0:
Worked with latest aokp and SmittyV. Cheers!
[Samsung Galaxy Nexus] AgentSmith:
Been using f2fs for quite some time now. It never gave me the feeling of having a faster phone but it does run smoothly and it doesn't seem to slow down over time. Fstrim is not supported so maybe the native f2fs clean process is doing its job properly. I really don't know how to check that though. Anyway, it's all fine and so far I haven't had a reason to go back to using ext4.
[Samsung Galaxy Nexus] sergialess:
For the record, the following 4.4.4 roms were converted and running fine:

- C-ROM v7.1

- OMNI FML working great, too.

- ShinyRom working properly after apk purge.

- Vanir (my beloved rom).
[Samsung Galaxy Nexus] chinarobin:
mokee failed，could boot but setting apk fc all the time
[Samsung Galaxy Nexus] poo706:
If you can both install and boot a converted rom on f2fs then my tool has done its job. I think you have something else going on there.

[poo]
[Samsung Galaxy Nexus] chinarobin:
maybe the rom problem, it worked fine under ext 4 before.
[Samsung Galaxy Nexus] sergialess:
Are you doing some apk purge? Make sure you don't delete talkback.apk, velvet.apk, wallet.apk, and try it again.

I've got the same problem with Settings Assistant, but with ShinyRom.
[Samsung Galaxy Nexus] poo706:
I didn't realize there were problems after purging those apps. Think we should make a new release?

[poo]
[Samsung Galaxy Nexus] sergialess:
Not sure at all. I had a problem finishing the setup with ShinyROM (Configuration Assistant FC, no launcher, booting problems, etc), but I figured out that some missing apks "could" be important in order to complete the installation. Or it's apk related, or perhaps it's kernel related.

Now I feel forced to test Mokee... :P
[Samsung Galaxy Nexus] poo706:
Yeah, probably shouldn't knee-jerk into a new release until we have some definite confirmation. Given how quiet the thread has been the last couple of weeks, I'm assuming no one is having troubles.

[poo]
[Samsung Galaxy Nexus] sergialess:
No doubt. The tool is definitely working great for me ;).
[Samsung Galaxy Nexus] KShion619:
What would you do to purge apks? Dont exactly know what that'd mean
[Samsung Galaxy Nexus] poo706:
When you convert /system to f2fs, you get less available space than ext4 for some reason. Shiny is too big because it includes gapps, so there's an option to purge some of those gapps to reduce the size of the rom.

[poo]
[Samsung Galaxy Nexus] chinarobin:
i didnot do anyting but follow the instructions, ext4 rom size is around 220mb, i also tried aokp rom modded for Chinese, and failed to flash, now i use the already converted liquid rom, feels good. i dont know what the problem is, since the tool is very friendly to use. Thanks very much for your hard and continuing work.
[Samsung Galaxy Nexus] danielstar13:
I think only fancy kernel is compatible with the rom when it goes through this tool?
[Samsung Galaxy Nexus] DR3W5K1:
^

What he said.

Try flashing a f2fs compatible kernel directly after flashing the ROM. I know of two off of the top of my head fancy and dirty v
[Samsung Galaxy Nexus] chinarobin:
probably rom problem or something related with it, cause i tried the c-rom, boots normally.
[Samsung Galaxy Nexus] poo706:
Post a link to the rom that you're having trouble with and I'll take a look at it.

[poo]
[Samsung Galaxy Nexus] chinarobin:
http://pan.baidu.com/s/1B3i8m compiled and modded with aokp

thanks
[Samsung Galaxy Nexus] poo706:
I ran your rom through my tool and it appears as though it's changing everything in the updater-script that it is supposed to. I notice though that the updater-script mounts /data. My first few releases didn't look for /data mounting and it caused problems when it wasn't addressed. Starting with the 7/7/14 release, this was fixed. What version are you running?

[poo]
[Samsung Galaxy Nexus] chinarobin:
EXT4_to_F2FS_gnex_2014-07-15_windows can you make it with this?
[Samsung Galaxy Nexus] poo706:
Hmm, and what goes wrong when you convert and install it?

I may need to dig deeper.

[poo]
[Samsung Galaxy Nexus] chinarobin:
it could be converted but not flashable
[Samsung Galaxy Nexus] poo706:
What error message do you receive when it fails to flash?

[poo]
[Samsung Galaxy Nexus] chinarobin:
dont remember much, something like fail....
[Samsung Galaxy Nexus] poo706:
I need to get to bed, but tomorrow I'll make you a last ditch effort test build for you to try. If that doesn't work, I'm out of ideas.

[poo]
[Samsung Galaxy Nexus] chinarobin:
thanks any way.
[Samsung Galaxy Nexus] poo706:
It occurred to me this morning that I don't need to make you a test build. The only thing I can possibly think is that /system isn't getting formatted like it should. Trying manually formatting /system, then install the ROM.

[poo]
[Samsung Galaxy Nexus] danielstar13:
Thank you for noticing!! :) I really needed help with this..

I see. I can still flash Fancy Kernel even though I've been using the ROM for a week. For DirtyV, once I flash it, the system fails to boot, it hangs in boot animation so I have to flash Fancy Kernel to get the system running back up again.
[Samsung Galaxy Nexus] chinarobin:
i tried it again, same error message,error update script....

i dont think the formatting problem that lead to it, i guess it would fail even under ext4, and i dont wanna get back to it.

let it away, since there are a lot of choice, like liquid, c-rom.

thank you so much.
[Samsung Galaxy Nexus] poo706:
I was going to recommend just letting it go anyway, so we're on the same page.

[poo]
[Samsung Galaxy Nexus] Pootch:
What about the GAPPS? Do i have to convert them too or just flash them afterwards?
[Samsung Galaxy Nexus] Hetalk:
No need to convert. Just flash after flashing converted ROM.
[Samsung Galaxy Nexus] sergialess:
Some issues with Dirty Unicorns v7.x and Windows version:

The problem is that the rom .zip file contains some files with same name in the same folder, with case-sensitive differences only.

For instance:

\system\media\audio\notifications\VEGA.ogg

\system\media\audio\notifications\Vega.ogg

So, for NTFS (Windows) they are the same, so the .zip file is invalid (7za.exe has some trouble working with it).

Solutions at this moment:

- Delete duplicated files (some .ogg)

- Do the conversion process manually :(
[Samsung Galaxy Nexus] poo706:
Surely that's a mistake that the DU devs didn't intend on. I think the best course of action is to bring this up with them and see if they'll fix the root of the issue on their end. If they won't for whatever reason, we'll see what we can do on our end.

[poo]
[Samsung Galaxy Nexus] sergialess:
Perfect. I'm going to inform the dev (Nasty007@XDA) right now.
[Samsung Galaxy Nexus] nasty007:
Hey, duplicated audio files are fixed and in upcoming builds it will be OK
[Samsung Galaxy Nexus] cujo6801:
Give it to me give it to me now!!

:D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] nasty007:
:) i will make new builds tomorrow
[Samsung Galaxy Nexus] sergialess:
Some users as Osmosis are commenting that having /system as F2FS may be useless (or even worse), because of its size, so they leave it as EXT4. /cache and /data remain F2FS.

If this is true, then the tool won't make much sense. updater-script replaces and F2FS-ready kernel won't be necessary.

Personally, I don't have any trouble having /system as F2FS. What do you think about this, Poo?.
[Samsung Galaxy Nexus] poo706:
Good question. I'm pretty sure a special kernel is still going to be required if any partition is on f2fs, but people could always flash that as a separate zip. The problem I have is that a few ROMs like SlimKat mount data as ext4, which will give you a google logo bootloop if data is actually f2fs. I think some people would run into troubles if they charge forward with "system is on ext4 and I have a special kernel, so I can install whatever I want".

One thing I can do is "format" system with "rm -rf /system" like I do on my universal liquidsmooth builds. Then people could run any ext4 ROM through the converter, even if it mounts data, and turn it into a universal ROM. We would just need to make sure to include a boot.img that supports mixing and matching ext4 and f2fs. I'm not sure if Fancy does or not.

[poo]

Edit: Well I'll be. Fancy r54 was just released and it does support mixing and matching file systems.
[Samsung Galaxy Nexus] Ashtrix:
Could you please explain why there's an disadvantage running system on f2fs ? , it seems fine here..:confused:

And the converted roms are they universal (mix and match friendly) ?

Thanks !!
[Samsung Galaxy Nexus] poo706:
The biggest disadvantage is that you end up with less space when you convert to f2fs, so converting system may limit you in ROMs and/or gapps. Also, it's just kind of pointless since /system doesn't see the amount of reading/writing that the other partitions do. Plus if system is ext4 you can install most ROMs without needing to convert, although you still have to worry about the kernel.

Mix and match kernels are only a very recent development on the gnex if I'm not mistaken. Fancy r51 that's included with the converter is not mix and match, but r54 that was just released a few days ago is. A recent dirtyv is as well. I should probably start including r54 with the converter...

[poo]
[Samsung Galaxy Nexus] sergialess:
Nicely explained. I think we'll end up leaving system as ext4 ;)

"Mix & Match"... hmmm.. it sounds like if we were DJs...
[Samsung Galaxy Nexus] Ashtrix:
So by just unchecking the force /system wipe function to f2fs will make it back to Ext4. That would suffice i guess, but the only thing is to reinstall the whole apps again, still i would try it sometime :good: !!

Thanks for the information poo ;) !!
[Samsung Galaxy Nexus] DR3W5K1:
Where's that BBQ reinvested guy at I think he's a DJ.

:TROLLFACE:
[Samsung Galaxy Nexus] GunFishin:
Converting Shiny Rom

Tried converting the latest Shiny rom (8/9/14) for my Maguro GN and it didn't work out. Followed these steps:

- Installed the TWRP for Maguro found on the DirtyV thread

- Wiped everything and converted file system to F2FS

- Used this converter tool to convert Shiny rom to F2FS (purged all APKs on the list to bring down file size)

- Flashed the converted Shiny rom followed by flashing the DirtyV kernel

Everything booted fine, but when I was completing the initial setup there was a force close, followed by the launcher not working. Everything was pretty much black. I could switch over to other apps, settings, etc but every time I hit the home button it would go to a black screen.

Not sure if I was supposed to flash GAPPS, did the conversion wrong or if I simply missed a step.

Couple of questions for the elite:

- Anyone successfully convert the latest version of Shiny (8/9/14) to F2FS? Would you be so kind to share that ROM with me? Otherwise, would you be able to briefly walk me through the steps taken to make everything work?

- Also, my phone is running at a decent pace using the latest Shiny (Shiny kernel as well), but from time to time performance is lackluster. How much of a difference does F2FS + DirtyV make compared to what I'm currently running?

Thanks to everyone that continues to work on the Galaxy Nexus and keeping my 2011 phone alive.
[Samsung Galaxy Nexus] poo706:
If you managed to install and boot the converted ROM, then my tool has done its job correctly. I suppose it's possible that the APK purge got rid of something that shouldn't have been gotten rid of. Although if that were the case I would think that someone else would have reported that by now.

[poo]
[Samsung Galaxy Nexus] GunFishin:
Well I appreciate the response, poo. I was thinking the same thing about purging APKs. Do you think flashing GAPPS after the ROM and KERNEL would fix such a problem?

Anyone else have a clue? Perhaps converted the latest version of Shiny? May have to go ask on the Shiny thread.
[Samsung Galaxy Nexus] poo706:
I can't imagine the kernel would make a difference, but I suppose it's worth a shot. The problem with Shiny is that it comes with gapps, which is what's making it too big on F2FS. Hard to say what would happen if you threw another gapps on top of what was already there.

If you're not super-dedicated to Shiny, I'd suggest just trying another ROM. At very least to see if it gives you FCs as well.

[poo]
[Samsung Galaxy Nexus] sergialess:
Be sure you don't remove velvet.apk nor talkback.apk. your Rom .zip file must contain these files.

Try and tell us. The same thing happened to me with ShinyRom. Missing important apks were the culprit (afaik).
[Samsung Galaxy Nexus] poo706:
Oh crap, I forgot you had told me about those. We should release a new version that fixes that.

[poo]
[Samsung Galaxy Nexus] sergialess:
Hi mate. I just started my vacation (at last). In two weeks we do whatever you want xD. Regards from the sunny beachs of Spain :P.

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] poo706:
So jealous! Get a hold of me when you get back. I'll probably go ahead and update everything and then we can do another Windows release when you get a chance to update the gui.

[poo]
[Samsung Galaxy Nexus] GunFishin:
Thanks! Will backup, try again soon and report back!
[Samsung Galaxy Nexus] GunFishin:
Thanks!

Just wanted to say thanks for the converter and help!

When purging the APKs for Shiny (8/9/14) ROM I left out velvet.apk and googletts.apk. Not sure if talkback.apk and googletts.apk are one in the same, but everything worked out fine this go around.

- Installed TWRP with F2FS support

- Formatted file system from EXT4 to F2FS

- Converted Shiny ROM (8/9/14) and purged all APKs except for velvet.apk and googletts.apk

- Flashed ROM

- Flashed DirtyV kernel

- Win!

Performance compared to EXT4 Shiny ROM + Shiny KERNEL is already noticeable.
[Samsung Galaxy Nexus] poo706:
Glad it worked out for you! Why did you choose to remove googletts and not talkback?

[poo]
[Samsung Galaxy Nexus] GunFishin:
You know, I didn't see talkback.apk on the list or when I opened the ROM zip. Want sure if googletts.apk was the same thing.
[Samsung Galaxy Nexus] poo706:
Heh, you're right about talkback. I think velvet was the key. Would you do me a huge favor and try deleting googletts to make sure that it's only velvet that needs to be kept?

[poo]
[Samsung Galaxy Nexus] GunFishin:
Flashed with googletts.apk purged and it worked fine. Velvet.apk is the key. You don't want to delete that for Shiny F2FS.
[Samsung Galaxy Nexus] poo706:
I'll be putting out new versions probably tomorrow, thanks so much for confirming.

[poo]
[Samsung Galaxy Nexus] poo706:
OP updated with new versions (except windows GUI). Velvet is no longer purged if you opt to purge APKs and Fancy r54 is now included.

[poo]
[Samsung Galaxy Nexus] [sito_web]:
Have you tried to root thw ROM? I can't root this awsome ROM.. I did the same things like you plus flash the root zip, bit it didn't work here. Does exist a particular root zip file for f2fs partition?
[Samsung Galaxy Nexus] sergialess:
I'll be updating the GUI on September 1st.
[Samsung Galaxy Nexus] poo706:
Sounds good, thanks!

[poo]
[Samsung Galaxy Nexus] GunFishin:
I didn't have any issue in rooting the converted Shiny ROM using the .zip included in the official Shiny thread: http://shinyrom.goofball.org/Universal Mods/UPDATE-SuperSU-v2.00.zip

Xposed + GravityBox are working for me. Try flashing that one. If you have already and it isn't working then I'm not sure why.
[Samsung Galaxy Nexus] [sito_web]:
Thanks for reply! Yes I have tried that file but don't work here I don't know why. I reflashed and format the system partition but nothing