It sounds like you're encountering a persistent boot loop issue after attempting to install Kernel SU on your Samsung Galaxy A06 with the specified kernel version and security patch. Here are some steps you can take to troubleshoot and potentially resolve the issue:

  1. Check Kernel Compatibility: Ensure that the Kernel SU version you're trying to install is compatible with your specific kernel version and device model. Sometimes, using an incompatible kernel can lead to boot loops.
  2. Revert to Stock Kernel: If possible, revert back to the stock kernel and reinstall Kernel SU. This can help determine if the issue is with the Kernel SU itself or if there's a conflict with your current kernel.
  3. Review Installation Steps: Go through the installation steps again carefully. Ensure that you're following the most recent and correct instructions for your device and kernel version. Sometimes, a small mistake in the installation process can cause boot issues.
  4. Check for Updates: Look for any updates to Kernel SU or your device's firmware that might address compatibility issues with your kernel version.
  5. Seek Community Help: Visit forums or communities dedicated to Samsung Galaxy A06 or Kernel SU. Other users might have faced similar issues and can offer solutions or workarounds.
  6. Use Alternative Methods: If GKI and LKM methods aren't working, consider trying alternative methods to install Kernel SU. There might be other approaches that are more compatible with your device.
  7. Flash Custom Recovery: If you haven't already, flashing a custom recovery like TWRP can sometimes help in resolving boot loop issues. It allows you to flash new kernels and mods more reliably.
  8. Check Logs: If you have access to logs from the boot loop, they can provide valuable insights into what might be going wrong. Look for any error messages or warnings that could point to the cause of the issue.

Remember to always backup your data before attempting any of these steps, as some of them can potentially result in data loss. If none of these suggestions resolve the issue, it might be worth reaching out to the developers of Kernel SU for further assistance.