@nero355 yes, twrp does f2fs

I search on github and found CyanogenMod/android_device_samsung_p5113. From this repo and cm.dependencies therein I suggest your manifest should look like <?xml version="1.0" encoding="UTF-8"?> <manifest> <remote name="github" fetch="https://github.com/CyanogenMod/" /> <project name="android_device_samsung_p5113" path="device/samsung/p5113" remote="github" revision="cm" /> <project name="android_device_samsung_p5100" path="device/samsung/p5100" remote="github" revision="cm" /> <project name="android_kernel_samsung_espresso10" path="kernel/samsung/espresso10" remote="github" revision="cm" /> <project name="android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm" /> </manifest> I'm not sure if it has properly settle down sources needed for your devices, please check it carefully. Btw, note that the docs you mentioned works for halium>=7.1, which based on cm>=14. However the latest support for your device is cm12.1. It seems that you should at first adapt your source to fix some new features provided from cm14. It is a huge work ... （Yay... in fact that is what I have experienced on my device... lol)

@geoeducativa said in a query about the device: zte nubia z5s mini nx406e: Use Halium 7.1 or Halium 9.0 Depending on the version of android shipped with your device. If your device once shipped with Android 9 you better use Halium 9. If your device is newer you'll have to try Halium 10 but it's not mature as far as I know. For older devices unsupported when Android 9 was released you should use Halium 7.1 for Android 7. If your device is even older than that I will not recommand to port...

@makeixo There are non halium ports, like my MX4, and halium 5, 7 and 9. There is not already halium 10 ports.

Hi, I found the correct configuration file and were able to fix this error: warning: (ANDROID_DEFAULT_SETTING) selects NETFILTER_XT_MATCH_QTAGUID which has unmet direct dependencies (NET && INET && NETFILTER && NETFILTER_XTABLES && NETFILTER_XT_MATCH_SOCKET && NETFILTER_XT_MATCH_OWNER=n) Unfortunately, the "make halium-boot" command ends with another error. https://pastebin.com/rHBrZcLD Does anyone know what to change so I can continue?

how about trying: (halium 9) huawei_kiwi.xml: <?xml version="1.0" encoding="UTF-8"?> <manifest> <remote name="LineageOS" fetch="https://github.com/LineageOS" revision="lineage-16.0"/> <remote name="TheMuppets" fetch="https://github.com/TheMuppets" revision="lineage-16.0" /> <project path="device/huawei/kiwi" name="android_device_huawei_kiwi" remote="LineageOS" revision="lineage-16.0" /> <project path="kernel/huawei/kiwi" name="android_kernel_huawei_kiwi" remote="LineageOS" revision="lineage-16.0" /> <project path="vendor/huawei/" name="proprietary_vendor_huawei" remote="TheMuppets" revision="lineage-16.0" /> </manifest>

[image: 1633380136270-nfc_test.jpg]

@nero355 Sorry I have no knowledge about that at all...

I have this same issue. Device I am trying to port is an Honor View 10.

@flohack ah thanks for that, I’ll stick to Halium for now then!

it was my mistake , initially when i run the mka mkbootimg I got this error error: vendor/xiaomi/whyred: MODULE.TARGET.SHARED_LIBRARIES.libsdm-disp-vndapis already defined by vendor/xiaomi/whyred. To resolve this I commented out those modules from vendor/xiaomi/whyred/Android.mk . I accidentally commented out libantradio module too . undoing that resolved the issue .

@aravindor Please mark as solved https://forums.ubports.com/topic/6311/how-to-ask-a-question-and-then-mark-it-as-solved

After a few days I decided to try another vendor.img and out of nowhere reboots worked just fine. I still have no idea why the vendor messed up apparmor but anyway, if someone happens to have the same problem he could try using different vendor images.

@carlo afaik that command should work, granted my knowledge is mostly LOS 14.1 based porting on a Galaxy Note 4, if that command is not working, double check the documentation your following is for the correct version of your LOS source, as well as your source is complete and not lacking anything.

@yxles Yes.