yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] qtoo941:
I guess i gotta flash R55 posted some hours ago by [MENTION=4615478]boype[/MENTION]. Have to see your feedback so i can get decision to flash it or to leave my phone like this. Today i got pissed off flashing different roms and kernels. Tried like 5 kitkat roms and 3 jellybean roms and like 6 kernels. In the end i flashed cataclysm.
[Samsung Galaxy Nexus] pvkiniyan95:
Is it f2fs compatible so that I can try converting 4.3.1 to f2fs with this kernel
[Samsung Galaxy Nexus] boype:
yes, go ahead
[Samsung Galaxy Nexus] SoftWord:
which Rom for gnex is version 4.3.1? I'm sure that the latest version is 4.3

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] pvkiniyan95:
Cool about to try...

Never mind, certain ROMs did a source update to nexus7 4.3.1 ROM, nothing special in it
[Samsung Galaxy Nexus] aliesz:
Hey boype what is this?! Is it a surprise?!;) thank you man..

Has it any change in compare with r54 test4-osmod?!
[Samsung Galaxy Nexus] qtoo941:
I got a question:

On R54_anykernel2 USB OTG was broken and [MENTION=4544860]osm0sis[/MENTION] posted some test4 version with fixed USB OTG. Is this fix included in R55?
[Samsung Galaxy Nexus] osm0sis:
It is the future! :silly:

Yes, it has the stuff from my attempt, plus another fix I had on DirtyV's that should allow USB-OTG on stockish 4.4 kernels that don't already have it for some reason.
[Samsung Galaxy Nexus] aosp:
[MENTION=4615478]boype[/MENTION] running great on omni so far ??
[Samsung Galaxy Nexus] qtoo941:
So I can finally flash Fancy R55 with Anykernel2 and fixed USB OTG on my JB ROM? Damn, you are good. I will try it soon and i will give me feedback to you.
[Samsung Galaxy Nexus] osm0sis:
Fingers-crossed buddy! I saw you had trouble on the last page so I'm worried there might still be some peice of the puzzle we're missing. I really want to see/help the GN Unified v2 AnyKernel2 zips work all the way back to 4.2, so that's why I've been hanging around more than usual. ;)
[Samsung Galaxy Nexus] siealex:
R55 still does not boot on PA 3.99. Flashed over the zipped stock kernel.
[Samsung Galaxy Nexus] osm0sis:
A dmesg/kmsg would be more helpful, can you do: dmesg > /sdcard/dmesg.txt while it's hung booting and post it? Thanks!

[MENTION=4615478]boype[/MENTION] I've got an idea, since this is AnyKernel we're talking about, the fsbase doesn't really need to be copied in, we could just use the ROM's original, then remove all the fstab workarounds since it should take care of itself. Might clear things up for the rest of people having issues.

I've also got to add a check that a matching file to swap from exists and if not do nothing. I'm hoping that will fix encryption again for v2, since I think the userdata entry was getting swapped out for nothing (removed) when blkid couldn't recognize it.
[Samsung Galaxy Nexus] siealex:
Trying...
[Samsung Galaxy Nexus] FredFS456:
I'm just two questions about the anykernel2 version:

- What is the advantage of that version over the non-anykernel version, if any? I read osm0sis's page on anykernel2, but that doesn't really describe the end-user benefits very well. If it's more compatible, so what? More compatibility for more ROM's?

- boype recommended that if we have a customized kernel that we flash the non-anykernel version. Does anyone know if PA has a customized kernel? I can't really find any information about that. I mean, it's an AOSP-based ROM, but it has a bunch of differentiating features, and has had custom kernel mods in the past.
[Samsung Galaxy Nexus] qtoo941:
I got a question:

Is it possible to compile Fancy Kernel similar or same to R54/R55 but only for JB 4.3 without AnyKernel2 included?
[Samsung Galaxy Nexus] osm0sis:
It's just for users of pre-KK Android versions, really, since boype maintains a KK ramdisked img. Generally it saves from making 4 different ramdisks for what is otherwise the same kernel. AnyKernel can also avoid issues like when CM added MultiSIM and every custom kernel with a ramdisk started crapping out because it was missing the msim jar in the bootclasspath; that's because it uses the ROM kernel's original underlying ramdisk so all the stuff the ROM expects to be there still is. AnyKernel2 then builds on that and lets kernel devs like boype add their own customizations easily. The best of both worlds.

The only trouble we were seeing was because the Unified v2 ext4/f2fs support that is being added via AK2 to the ramdisk replaced the older ROMs' fstabs with things that they couldn't handle, and which we've been working on resolving.

See above. AnyKernel is just a way to avoid having to maintain several ramdisks. It's all the same kernel compile.
[Samsung Galaxy Nexus] osm0sis:
Okay those who still had problems with boype's r55-test on 4.2.x or 4.3, what's this do? :)

[ Attachment removed, I've got a newer test version up ]
[Samsung Galaxy Nexus] klingklang76:
I used to think that flashing kernel was sort of an ultra-nerd-high-end-fine-tuning, more likely to make your device unstable rather than faster or better... but as my Gnex is approaching its end of life, I decided to give it a go. With CM11 M9, performance has improved dramatically, but not as much as battery life: I won't say doubled but definitely in that neighborhood. A really pleasant surprise, thank you so much for your brillant work! :)
[Samsung Galaxy Nexus] Bazzu:
Guys i'm running omnirom FML and it seems to be very good (before omni fml i had official omnirom and liquid rom)! I flashed r54 and yes it gives a nice boost but i didn't find yet a rom+kernel combination that makes me love 4.4.4...i don't know if i should change some settings in the kernel but what i experience every time is "oh nice, this time seems to be fast enough"..but after 2 minutes i find typical little/big lags etc

When i flash a new rom i usually do 4 wipes...so i don't know why but after 2/3 months a clean using wugfresh's toolkit seems to be needed :/

Please help me :what:

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] piterdemon:
Please dwnl "fstrim" app from google play and trim /system /data and /cache

Wytapatano z Galaxy Nexus PA 4.5 beta2 [MENTION=280772]Dirty[/MENTION]Vkernel
[Samsung Galaxy Nexus] cabalio83:
Reboot

Hi there..

I am using a spare battery on my gnex so I reboot the phone quite often when I do the swap. (usually every two days, once a day if I use it a lot).

I've noticed that at every boot the phone goes to the lockscreen and then eventually reboot.

The next boot is fine.

Wich log would be useful to you? Just let me know.

I had this on the latest build as far as I remember (R53 and 54).

I'm running FML Omni on f2fs if that matters

Except this Fancy is awesome.. Great work

Ps I had CAB disabled in Trickster mod
[Samsung Galaxy Nexus] Bazzu:
I forgotten that fstrim saved me so many times :D

But this just happened to me: " i'm running omnirom with r54 fancy kernel.

My doubt is: i don't understand why 10 minutes ago i downloaded free version of your app and it trimmed /data and /cache partitions, then i tried the full version after the download, but said partitions weren't available anymore because of the kernel :/ ... is it possible?

Can be useful trim only the /system partition? "

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] GilGameshn1:
If you are on f2fs ... Then yo don't need fstrim ... F2FS have a garbage cleaning system ... Take care .?
[Samsung Galaxy Nexus] taylerdurden:
Since Android 4.3, the system do the FSTRIM automatically sometimes, so using external apps is useless
[Samsung Galaxy Nexus] GilGameshn1:
Fstrim not working in F2FS ...
[Samsung Galaxy Nexus] taylerdurden:
I mean in EXT4
[Samsung Galaxy Nexus] GilGameshn1:
Then you are right ... ?
[Samsung Galaxy Nexus] siealex:
IT BOOTS!!!

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] Bazzu:
I know man, but i have one of that gn with the famous problem of lags when coping/reaching etc an amount of space in phone's memory..and lagfix helped me for a long time

I Mm i don't think to have f2fs..did nothing to have it :)

Anyway the developer said me that there was a bug -> so i had to clean app data in settings>apps :sly:

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] infectedorganism:
On 4.2.2, I've had no problem with either your or boype's version of r55 test; both boot and both retain access to internal storage.
[Samsung Galaxy Nexus] piterdemon:
Nope, You still must do it manually. If its automatical then why I had 5mb read and 1mb write ? After trim i have 30mb read and 21mb write so automatical fstrim never exist

Wytapatano z Galaxy Nexus PA 4.5 beta2 [MENTION=280772]Dirty[/MENTION]Vkernel
[Samsung Galaxy Nexus] siealex:
Why does r55 set my CPU to 224 MHz instead of 192?

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] aSKAp6uH:
replace 192 MHz CPU step with 224 MHz for failsafe reasons (seriously, trust me when I say that you don't have to worry about increased power consumption)

It's cool decision. PowerAmp working smooth now.
[Samsung Galaxy Nexus] bsmitty83:
192mhz was dropped for 224mhz , its the lowest freq on fancy now . [emoji106]
[Samsung Galaxy Nexus] qtoo941:
[MENTION=4544860]osm0sis[/MENTION] - thank you mate. It finally booted. Was using cataclysm with mpokang, dirty flashes original cataclysm and finally flashed your fixed r55 with ak2. Booted! Not even bootloop! Nice. Gotta go home and check if usb otg is working.
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=4615478]boype[/MENTION] now 4.3 works like a dream in f2fs with ur kernel....i m ditching kitkat now...but for some reason while converting to f2fs the boot.img i used was of vanir's 4.3 roms. no other roms boot.img works... [MENTION=4608636]bsmitty83[/MENTION] a dirtyV anykernel sounds pleasing too..keep up the gr8 work buddies...

TUNA rules.....guys try 4.3 once in f2fs and u will love it NOVA pretty much gives u the kitkat experience
[Samsung Galaxy Nexus] aliesz:
Excuse me [MENTION=4615478]boype[/MENTION], why the new r55 build is not presented on OP? And how we can know change logs of recent releases?
[Samsung Galaxy Nexus] aosp:
Not ready yet maybe?
[Samsung Galaxy Nexus] joelmonty:
I had tried boype version but it didn't work, then I tried this it's working,thanks Osmosis and boype.

Truly amazing kernel.
[Samsung Galaxy Nexus] alexcavaco:
Hello,

This worked fine on my stock 4.3 rom.

This was my first attempt (I skipped previous test versions).

I dirty flashed the stock rom and then flashed your version.

No problems so far, no reboots, no FCs.

Thanks! :)
[Samsung Galaxy Nexus] qtoo941:
Aaand another question:

So now I am using JB ROM (Cataclysm if it makes any sense) with Fancy R55 Test4_AnyKernel2 which [MENTION=4544860]osm0sis[/MENTION] posted some pages ago. And lets say that in next days you will release R55 and will not be the same as osm0sis's one but the same with some fixes or optimizations (just for example). What shall I do when i try to flash it? Once again going back to stock rom kernel and again flashing new release of Fancy or just wiping cache and dalvik and flashing newer version of Fancy?
[Samsung Galaxy Nexus] osm0sis:
Except that a lot of people don't meet the 24hr uptime requirement of the internal fstrim, so it never gets to run. ;)

Booyah, we have a winner! :D

Can all you guys post the contents of your fstab.tuna so we know it worked 100%?

I wouldn't worry about it being different. The whole point of the r55 test versions so far has been to get it working for you and others like you, so I'd imagine the final r55 will have the same changes as my latest attempt. :)

That said, yes, the correct procedure to upgrade would be to flash your ROM kernel again then the newer Fancy AK2 zip.

Writing up a smarter fscheck to commit to DirtyV now, which [MENTION=4615478]boype[/MENTION] can then grab. :D :good:
[Samsung Galaxy Nexus] qtoo941:
# Android fstab file.

#<src> <mnt_point> <type> <mnt_flags and 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_CHECK

/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro wait

/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro wait

/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,discard,errors=panic wait,check

/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit,discard,errors=panic wait,check,encryptable=/dev/block/platform/omap/omap_hsmmc.0/by-name/metadata

/dev/block/platform/omap/omap_hsmmc.0/by-name/misc /misc emmc defaults defaults

/dev/block/platform/omap/omap_hsmmc.0/by-name/boot /boot emmc defaults defaults

/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery /recovery emmc defaults defaults

/dev/block/platform/omap/omap_hsmmc.0/by-name/sbl /sbl emmc defaults defaults

/dev/block/platform/omap/omap_hsmmc.0/by-name/xloader /xloader emmc defaults defaults

/dev/block/platform/omap/omap_hsmmc.0/by-name/radio /radio emmc defaults defaults

So finally when i am on Fancy i cannot just wipe cache and dalvik but i have to get stock kernel again? Why? I thought from now i must just wipe cache/dalvik and flash just the newer version of Fancy. Ooouh, okay. Okay. No problemo! Waiting to see final R55 with new things from DirtyV as you mentioned
[Samsung Galaxy Nexus] osm0sis:
Because you're on AnyKernel zips now, and they require a clean base to flash upon, like your ROM kernel's ramdisk. Check out boype's knowledgebase on AnyKernel from the OPs as well as his different instructions for flashing. :good:

Oh, and OTG may or may not work depending on whether your ROM's kernel supported it in the first place. I figured we should worry about getting it to boot first and then maybe see about adding back the OTG stuff (for ROMs that don't have it) later.

Bad news is, it doesn't appear to have swapped the entries for you, and it should have. I'll keep looking into it. :(
[Samsung Galaxy Nexus] joelmonty:
# Android fstab file.

#<src> <mnt_point> <type> <mnt_flags and 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_CHECK

/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro wait

/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro wait

/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check

/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/omap/omap_hsmmc.0/by-name/metadata

/dev/block/platform/omap/omap_hsmmc.0/by-name/misc /misc emmc defaults defaults

/dev/block/platform/omap/omap_hsmmc.0/by-name/boot /boot emmc defaults defaults

/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery /recovery emmc defaults defaults

/dev/block/platform/omap/omap_hsmmc.0/by-name/sbl /sbl emmc defaults defaults

/dev/block/platform/omap/omap_hsmmc.0/by-name/xloader /xloader emmc defaults defaults

/dev/block/platform/omap/omap_hsmmc.0/by-name/radio /radio emmc defaults defaults
[Samsung Galaxy Nexus] qtoo941:
I also got some file like fstab-ext4.tuna . Is it needed?
[Samsung Galaxy Nexus] osm0sis:
What?! Are you booted to your device right now? That should get removed no matter what.

Edit: It's like fscheck isn't even being run for some reason..

joelmonty, your fstab didn't change either, so I guess we've got a trend between who it works for and not.
[Samsung Galaxy Nexus] joelmonty:
After flashing I had lost root though, I haven't checked if otg works, will check later, and to get root back I flashed chain fires zip got root back but lost super user apk, so I installed that from play store, this same thing happened on 4.4 too when I flashed fancy kernel.

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

It's there for me too,Should I manually delete it?
[Samsung Galaxy Nexus] osm0sis:
Something is up with the execution of the fscheck script. Can you two guys post your init.tuna.rc files?
[Samsung Galaxy Nexus] osm0sis:
Looks good. So weird.

P.S. [code][/code] blocks are awesome for things like that in the future. :)

Edit: Just flashed the new fscheck via ramdisk on my device and it correctly swaps out for f2fs partitions and removes the fstab-<fstype>.tuna files and everything. It's slightly different, so I'll put up a new version with it shortly to see if it helps anything..
[Samsung Galaxy Nexus] osm0sis:
And then?

[MENTION=5327279]qtoo941[/MENTION] [MENTION=3793820]joelmonty[/MENTION] [MENTION=1097461]siealex[/MENTION] [MENTION=4078274]infectedorganism[/MENTION] [MENTION=4920659]namtombout[/MENTION] [MENTION=1159566]alexcavaco[/MENTION] [MENTION=2838735]aosp[/MENTION]

(Remember to flash over your ROM kernel's boot.img. Provided it boots, which it should no matter what now, please give me fstab.tuna [in code blocks please!], and also tell me whether there are still extra fstab-<fstype>.tuna files kicking around. My new fscheck definitely works in the ramdisk version on KitKat.)

[ Attachment removed. r55 official with these fixes is out! ;) ]
[Samsung Galaxy Nexus] aliesz:
Boype's r55 kernel works correctly here on 4.3 JB stock ROM.
[Samsung Galaxy Nexus] osm0sis:
Yup. Working on the outliers now. ;)
[Samsung Galaxy Nexus] aliesz:
What do you mean?!
[Samsung Galaxy Nexus] osm0sis:
People who boype's r55 still didn't work for. :good: :)
[Samsung Galaxy Nexus] aliesz:
But it works for me, I don't know what the reason is but when I dirty flash new builds over the last stable fancy kernel special for jb (r43 -ext version ) then wipe cache and dalvik cache, they work correctly. Everybody can try it. ;)
[Samsung Galaxy Nexus] boype:
Sorry to just ask without reading through the last pages (little stressed these days), but:

Is everything working now as it should? I'll finalize r55 and push sources/changelog etc.

p.s.: thanks a bunch for hanging in there. That counts for the testers too!:good:
[Samsung Galaxy Nexus] osm0sis:
That's not the correct method for flashing. Just a workaround. You should flash over your ROM's kernel.

Haha I don't blame you for not reading all that. Sorry for cluttering up the place! ;)

Using the original ROM fstab definitely got the outliers to boot, but for some reason it appears that fscheck isn't being executed on their devices. That'll be confirmed if they try my latest zip above and your fstab changes still haven't been swapped in.

Since init.tuna.rc looked fine, I'm starting to think we might be dealing with old versions of the init binary in their old ROM kernel's ramdisks that don't support the exec command.

If that's the case, I'm not sure how to work around it (KitKat's might be back compatible?), but perhaps leaving it like I have it would be the best we could hope for; Unified v2 f2fs/ext4 works on any modern ROMs where init supports exec, and the original fstab remains on those that don't.
[Samsung Galaxy Nexus] alexcavaco:
Sorry, did not see this earlier. I've just flashed your new test version.

I still have fstab-ext4.tuna and fstab-f2fs.tuna files. I'm using ext4

Here is my fstab.tuna:

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and 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_CHECK

/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro wait
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro wait
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/omap/omap_hsmmc.0/by-name/metadata
/dev/block/platform/omap/omap_hsmmc.0/by-name/misc /misc emmc defaults defaults
/dev/block/platform/omap/omap_hsmmc.0/by-name/boot /boot emmc defaults defaults
/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/omap/omap_hsmmc.0/by-name/sbl /sbl emmc defaults defaults
/dev/block/platform/omap/omap_hsmmc.0/by-name/xloader /xloader emmc defaults defaults
/dev/block/platform/omap/omap_hsmmc.0/by-name/radio /radio emmc defaults defaults
[Samsung Galaxy Nexus] osm0sis:
Hmm so same issue with it not executing but that might be the init binary's fault. What are the permissions on fscheck?
[Samsung Galaxy Nexus] alexcavaco:
The permissions on fscheck are 0750 (rwxr-x---)

Btw, when dirty flashing before trying this test version, I've flashed just my stock boot.img, did I need something else?
[Samsung Galaxy Nexus] osm0sis:
Nope that's correct. Since I think you said you hadn't tried it yet, can you try boype's r55 from a few pages back? I need to know if fscheck not executing is something new and weird or if it's a constant for the people it wasn't already working for.

Same procedure: stock/ROM boot.img then the AK2 zip.
[Samsung Galaxy Nexus] namtombout:
I doubt f2fs fixed the major ram leak in 4.3.
[Samsung Galaxy Nexus] 7175:
Much thanks for the updates boype. Running the fixed ram-disk r54 on 4.4.4 Carbon with ext4, no problems at all, buttery smooth with nice battery and a nice frequency usage distribution. Also thank you for including an anykernel2 version. I've been looking for these tools! Can't wait to start taking thing apart and get back my custom sbin.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4615478]boype[/MENTION], I'd say you're good to go with what I've got in my last zip. fscheck may not be executing on some old ROMs for some reason (my only theory is the exec command isn't accepted by their old init binary, or maybe there's something wrong with the busybox ash shell on their old versions?), but I just flashed it over Carbon 4.4.4's boot.img and it most definitely swapped in both your ext4 and f2fs tweaks perfectly, and I'm running ext4 /system and f2fs on /data and /cache. ;)

..So I'm pretty satisfied; I also got confirmation that my added check fixes (at least) ext4 encryption. Changes are up on the DirtyV GitHub already. :)

It's definitely the best we can do for now (i.e. it will basically always boot!) until you want to start experimenting with using a known working 4.4.x or 4.3 init binary in the AnyKernel2 zip to see if that fixes fscheck execution on the outlier older ROMs. I would just caution people to only use f2fs on KitKat ROMs unless they know fscheck functions (e.g. no fstab-<fstype>.tuna files laying around) on their <=4.3 ROM. :good:

Anyway, thanks for the fun week in Fancy Land guys! I'm headed back over to Dirty Town now. :p :highfive:

Oh, P.S., can you make it say AnyKernel2 by osm0sis @ xda-developers in your updater-script instead of "AnyKernel Script" ? It fits on one line in TWRP that way. Thanks!
[Samsung Galaxy Nexus] aliesz:
Do you mean I may have any problem in future? :confused:
[Samsung Galaxy Nexus] osm0sis:
Yes. You're ignoring everyone's instructions and flashing it incorrectly. Of course that could cause problems.

Think about it: you're overlapping Fancy r43's tweaks with r55's; the r55 ones should win but we can't guarantee it doesn't break something in the process.

boype and I have both reiterated many times that AnyKernel2 zips should be flashed over your basic ROM kernel boot.img so that you have a clean slate. Consider yourself warned (..yet again).
[Samsung Galaxy Nexus] lparcshinoda:
Should I flash -> boot -> flash to be sure?
[Samsung Galaxy Nexus] alexcavaco:
I just tried it now, it rebooted just after first boot and then got stuck on startup (same users had the same problem with that version)...

Inside the recovery there is just fstab.tuna and fstab.goldfish, no other fstab's. But fscheck is not present, so maybe the first boot didn't ran well.

I flashed back to your latest test now.

Thank you and boype!