Database Users

Confused

So when I install a rom like SlimKat I need to have installed a TWRP recovery with F2FS and repartition it, too?
But then. When I have SlimKat (I think this seems to be a good rom but I let anyone join in to say what would be better) there are no gapps in it and here there seems to be Dalvik or ART Gapps on which ART would be better. SO where do I get ART Gapps for SlimKat (or other recommend roms)?

Gapps don't depend on art or dalvik. Any Gapps made for the Android version of the rom is all you need.
And no repartitioning is needed to install a rom. ?

Could you explain to me if f2fs is needed somehow (eg. makes the device faster etc.) or should I stay on the latest original rom from google until Version "L" comes out?
There is something I have read about new kernels in older roms is this needed for some things?

Custom kernels are never "needed"... Usually.
And sorry, I know nothing of f2fs.
?

Grand Prime not booting AOSP ROMs

Please help me! To all the developers whom i know of?
@KoSett @Has.007 @zim555 @Boulaxx
My variant G530FXXU does not boot AOSP and MiUi roms mainly all the other roms other than Sammy roms.
My device boots each of the sammy roms.
Several users with the same g530f did report that AOSP extended and RR and LineageOS roms successfully boot in their phones.
Even the 5.1.1 roms like Cyanogenmod 12.1, RR 5.1.1 and LiquidDark does not boot for me even after flashing ExplosionKernel (by @CarlosArriaga ) which is supposed to work because Explosion Kernel boots for me on every Samsung rom. (5.0.2 or 5.1.1)
So, its probably not anything to do with the kernel, I saw in another thread about wiping preload partitions, i did manually try wiping the preload partition via TWRP File manager yet doesnt work.
I found a thread that explains my situation here(the exact same situation). I really want to try any Google rom, Please help me.
This is the thread: https://forum.xda-developers.com/galaxy-s3/help/solved-galaxy-s3-booting-aosp-aokp-t2775669
Id be really grateful,
Thanks,
Eden532

Need Some Help For NOS Latest Treble Build..

Hello Everyone Thnxx For Your Attention I'm Currently On RR Oreo N I Want To Flash Latest Build Of NOS Treble Build I Have No Idea How To Flash It Any Help Will Be Appreciated Thnxx..

Azzkaran said:
Hello Everyone Thnxx For Your Attention I'm Currently On RR Oreo N I Want To Flash Latest Build Of NOS Treble Build I Have No Idea How To Flash It Any Help Will Be Appreciated Thnxx..
Click to expand...
Click to collapse
Firstly, flash TWRP-treble version.
Preferably wipe everything (except maybe internal storage)
And then install any ROM you want. (Both treble and normal ones)
Enjoy!

Falcon_fan said:
Firstly, flash TWRP-treble version.
Preferably wipe everything (except maybe internal storage)
And then install any ROM you want. (Both treble and normal ones)
Enjoy!
Click to expand...
Click to collapse
Installed ty:silly:

How do I install a stock kernel?

Looking to install a stock kernel somehow but i'm not sure how exactly. is there any guide on how to install a stock kernel? I've already looked arrount the forums but didn't really find any usefull information.
I'm rocking a xxx41 model and I'm planing to install Invicta OS onto it.
Thanks for any help in advance.

pissgoat said:
Looking to install a stock kernel somehow but i'm not sure how exactly. is there any guide on how to install a stock kernel? I've already looked arrount the forums but didn't really find any usefull information.
I'm rocking a xxx41 model and I'm planing to install Invicta OS onto it.
Thanks for any help in advance.
Click to expand...
Click to collapse
I have already replied same thing on older thread, [ https://forum.xda-developers.com/moto-g4-plus/help/quick-questions-kernel-installations-t3794980 ]
if you flash ROM, it will also install kernel which is considered stock for that installed ROM. You need to flash kernel only if you have modified it (by flashing custom kernel or SU zips).
If you want to flash different ROM, you can flash without doing anything else, just wipe and flash.
PS invictaOS is discontinued long ago, invictaOS-Nougat is stable, Oreo will be more bugfull than current available ROMs..

Experience "failure to load kernel" issue after flashing lineage 17 OS and OpenGapps 10 stock... please share the solution.. do i need to load a stock kernel?

veikaas11880 said:
Experience "failure to load kernel" issue after flashing lineage 17 OS and OpenGapps 10 stock... please share the solution.. do i need to load a stock kernel?
Click to expand...
Click to collapse
Though these forums are for the Moto G4 Plus, that does suggest an issue with the build of Lineage OS that you're using. Can you confirm with the developer that this build is successfully running on their device? Do you have a compatible Lineage 17 OS based kernel you could try to flash?
Was your device working with other stock or custom ROMs before flashing Lineage 17?

F2FS loopback bug?

Hi, do you guys know if Mate 10 Lite suffers from F2FS loopback bug? I have a problem installing any Adblock, Viper4FX and possibly other plugins I haven't tested yet. SELinux permissive doesn't fix anything as well as MorfuZ v2.1 kernel. F2FS loopback bug workaround zip can't be installed as I tried both Magisk stable and beta and zip doesn't find Magisk installed. Any ideas? Anyone has the same problem?

its not a f2fs bug
i think this is a emui-8.0 bug rather than a f2fs, because viper4android and dolby atmos is working in any GSI rom (gsi rom is stock google rom)
*i tested to flash the dolby atmos as well on EMUI and it just bootloops even with any ports from blu or other phones. but later tested the same dolby atmos.zip file in stock gsi oreo and it worked. The rom (MorfuZ V3.6, by catuva) managed to include a dolby atmos paired in a music app and not system wide, maybe audio manipulation app wont work on emui and will only work on individual app like the music app in Murfuz Rom.
ps, device id is Nova 2i - Rne-L22(636) / aka: Mate 10 lite SE-asia version.

shizuni said:
i think this is a emui-8.0 bug rather than a f2fs, because viper4android and dolby atmos is working in any GSI rom
Click to expand...
Click to collapse
But isn't that caused by the fact that EMUI 8.0 introduces some AI algorithms and F2FS? I checked the filesystem of all the partitions and grep'd "F2FS" and userdata was formatted F2FS.