I'm thinking of adding a Custom ROM to a Samsung A series phone (One UI 7) and it would be my first time doing Custom ROM. I want to do it to remove bloatware and especially the spyware app iron source but if I do it will it break Knox?

I also want privacy and security too (like Graphene OS as that's the best and even beats Knox) but what are the risks? does tripping Knox break security/privacy? if so in what way? as I heard it's important to have Knox.

I don't own a PC so can you do it at a computer shop? I don't wanna buy a computer just to ROM.

Edit: All I'm asking is if I trip the Knox fuse will I be at risk security wise? Or will the custom ROM still protect me as it might provide better security? (Like how graphene does os on pixel)... Simple really and I couldn't care less about NFC or Google Pay or whatever and no my phone won't get stolen

In attemps to build a non gsi lineage os 15.1 Rom, ngl was prompting AI for error resolving, which eventually worked out to create the generic build without a build scripts (I opted for this to better understand the errors and process for future refferences).

However, now that this is the case, in attempts to build device specific target (with no git release source tree/opensource repo) I was left with two options

1) build the target (hardcoded within the main lineage common file:

Alternative: Bypass AndroidProducts.mk

If the file persists as problematic, you can temporarily hardcode the path by editing how the build system finds products. But first, let's verify the current file is valid:

bash

# Test if Make can parse the file

cd ~/lineage

make -f /dev/null --eval='include device/tcl/U3A_PLUS_4G/AndroidProducts.mk' --eval='$(info PRODUCT_MAKEFILES=$(PRODUCT_MAKEFILES))' 2>&1 | grep "PRODUCT_MAKEFILES"

# Expected output:

# PRODUCT_MAKEFILES= device/tcl/U3A_PLUS_4G/lineage_U3A_PLUS_4G.mk

If this fails or shows empty, the file has syntax errors.

Or

2) build outside of 'lunch' targets, since appareantly, this selfmade repo structure does not compat well with or is undocumented for builds below 17.1.(specifically the AndroidProducts.mk detection is to be alligned with 17.1 builds, so I'm unsure what differs with 15.1 and it's needed files)

~/lineage$ ll device/tcl/U3A_PLUS_4G/

total 60 drwxrwxr-x 4 ubuntu ubuntu 4096 Sep 3 08:07 ./

drwxrwxr-x 3 ubuntu ubuntu 4096 Aug 22 17:04 ../ -rw-rw-r-- 1 ubuntu ubuntu 189 Aug 22 17:01 Android.bp

-rw-rw-r-- 1 ubuntu ubuntu 282 Aug 22 16:59 Android.mk

-rw-rw-r-- 1 ubuntu ubuntu 344 Sep 3 07:40 AndroidProducts.mk

-rw-rw-r-- 1 ubuntu ubuntu 2282 Sep 3 07:22 BoardConfig.mk-rw-rw-r-- 1 ubuntu ubuntu 4084 Sep 3 07:53 U3A_PLUS_4G.mk

-rwxrwxr-x 1 ubuntu ubuntu 1752 Sep 3 07:08 extract-files.sh* -rw-rw-r-- 1 ubuntu ubuntu 885 Sep 3 05:48 lineage_U3A_PLUS_4G.mk

drwxrwxr-x 2 ubuntu ubuntu 4096 Aug 22 17:13 prebuilt/ drwxrwxr-x 3 ubuntu ubuntu 4096 Aug 22 16:59 recovery/

-rw-rw-r-- 1 ubuntu ubuntu 4506 Aug 22 16:59 recovery.fstab

-rwxrwxr-x 1 ubuntu ubuntu 1301 Sep 3 07:08 setup-makefiles.sh*

-rw-rw-r-- 1 ubuntu ubuntu 245 Sep 3 05:43 vendorsetup.sh

________ this is all I'll be manually dumping, not going to clog up with images either, will just .txt the issues/solutions given I have it they are too long.

Nevertheless, i'm not about to go through 'rabbit hole' solutions when the model speculates too far from actual issues closer to what is needed. For example, claiming corrupt fs or files. ↓

''Quick Fix Script Run this to sanitize all your makefiles:''

~/lineage$ lunch lineage_U3A_PLUS_4G-userdebg build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_U3A_PLUS_4G". Stop. Device U3A_PLUS_4G not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS). Failed to search GitHub build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_U3A_PLUS_4G". Stop. build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_U3A_PLUS_4G". Stop.

** Don't have a product spec for: 'lineage_U3A_PLUS_4G' ** Do you have the right repo manifest?

I hope this was consice enough to seek out a solution, will wait for a help responce 💪🏽🙏🏾.