[Magisk] sergej_7:
So a few findings from my side:

One app Barclays (https://play.google.com/store/apps/details?id=com.barclaycard.germany) is checking the contents of addon.d folder. This can be fixed by creating the following script which was created by ChatGPT under /data/adb/modules/addon-d/post-fs-data.sh with 755 rights:

#!/system/bin/sh

# Define the path to be removed and the mount point

TARGET_PATH="/system/addon.d"

MOUNT_POINT="/mnt/empty"

# Create an empty directory to use as the mount point if it doesn't exist

if [ ! -d "$MOUNT_POINT" ]; then

mkdir -p "$MOUNT_POINT"

log -t Magisk "Created mount point at $MOUNT_POINT"

fi

# Check if the path exists

if [ -d "$TARGET_PATH" ]; then

# Bind mount the empty directory to the target path

mount --bind "$MOUNT_POINT" "$TARGET_PATH"

# Log the action

log -t Magisk "Bind mounted $MOUNT_POINT to $TARGET_PATH in post-fs-data.sh"

else

log -t Magisk "$TARGET_PATH does not exist in post-fs-data.sh"

fi

maybe snake-4 can implement this as part of zygisk assistant to improve root hiding further.

Another thing which Momo detected: "init.rc modified". Removing "install-recovery.sh" from /system/bin and /vendor/bin gets rid of this detection. This can be fixed by creating the following service.sh created by ChatGPT with 755 rights under /data/adb/modules/install-recovery/

#!/system/bin/sh

# Check and remove /vendor/bin/install-recovery.sh

if [ -f "/vendor/bin/install-recovery.sh" ]; then

/system/bin/mount -o rw,remount /vendor

rm -f /vendor/bin/install-recovery.sh

/system/bin/mount -o ro,remount /vendor

fi

# Check and remove /system/bin/install-recovery.sh

if [ -f "/system/bin/install-recovery.sh" ]; then

/system/bin/mount -o rw,remount /system

rm -f /system/bin/install-recovery.sh

/system/bin/mount -o ro,remount /system

fi

the reset-los-props module didnt work for me. The app PAYBACK (https://play.google.com/store/apps/details?id=de.payback.client.android) was still recognizing that my device is running LineageOS. I have used your module as base and created a new service.sh with the help of ChatGPT which can be copied to /data/adb/modules/reset-los-props/service.sh with 755 rights:

#!/system/bin/sh

# Define paths

TARGET_PATH="/system/build.prop"

MODIFIED_BUILD_PROP="/data/adb/modules/reset-los-props/build.prop"

# Remove existing modified build.prop if it exists

if [ -f "$MODIFIED_BUILD_PROP" ]; then

rm "$MODIFIED_BUILD_PROP"

fi

# Check if modifying "lineage_" or "lineage" would result in any changes

if grep -q 'lineage_' "$TARGET_PATH" || grep -q 'lineage' "$TARGET_PATH"; then

# Copy build.prop to module directory for modification

cp "$TARGET_PATH" "$MODIFIED_BUILD_PROP"

# Remove the terms "lineage_" and "lineage" from the copied build.prop file

sed -i 's/lineage_//g' "$MODIFIED_BUILD_PROP"

sed -i 's/lineage//g' "$MODIFIED_BUILD_PROP"

# Fix any occurrences of double dots to single dot

sed -i 's/\.\././g' "$MODIFIED_BUILD_PROP"

# Mount /system as read-write

mount -o rw,remount /system || mount -o rw,remount / || mount -o rw,remount /dev/block/bootdevice/by-name/system /system

# Replace the original build.prop with the modified one

cp "$MODIFIED_BUILD_PROP" "$TARGET_PATH"

# Remount /system as read-only

mount -o ro,remount /system || mount -o ro,remount / || mount -o ro,remount /dev/block/bootdevice/by-name/system /system

fi

# Reset additional sensitive properties

resetprop -n ro.boot.flash.locked 1

resetprop -n ro.boot.vbmeta.device_state locked

resetprop -n ro.boot.verifiedbootstate green

resetprop -n ro.boot.veritymode enforcing

resetprop -n vendor.boot.verifiedbootstate green

resetprop -n vendor.boot.vbmeta.device_state locked