Ravindu Deshan

> Building a custom kernel image with disabled Samsung security drivers ([BlackMesa123/android_kernel_samsung_sm7325@7569eb2](https://github.com/BlackMesa123/android_kernel_samsung_sm7325/commit/7569eb2c1549a98f0edef3c2d22d92d2211aaa1d)) solves this. > > > > Perharps extra patches are required to handle Samsung shipped kernels? > >...

> > Could I patch using Magisk boot to disable security features and then patch with APatch? > > As explained in [#123 (comment)](https://github.com/bmax121/APatch/issues/123#issuecomment-1890473160), those patches are old and don't...

> > Could I patch using Magisk boot to disable security features and then patch with APatch? > > As explained in [#123 (comment)](https://github.com/bmax121/APatch/issues/123#issuecomment-1890473160), those patches are old and don't...

> any help ? Do not enable the system framework for the module. Only add the "WhatsApp" package.

I was able to dump the log files related to this incident using Magisk (from /data/adb/ksu/log: [log_m14_ksu.zip](https://github.com/user-attachments/files/17153046/log_m14_ksu.zip) edit : I was not able to find anything important in these logs....

**Quick update:** After wasting over 5-10 hours in the debugging process, I finally managed to identify why this happens and found a workaround to fix the issue. I always thought...

> Is your terminal a 32-bit application? maybe. btw this issue happened with half of my root related apps, even with the root explorer. Only shizuku and log fox worked...

> try this one: https://github.com/tiann/KernelSU/actions/runs/10977394262?pr=2084 okay, lemme check

> try this one: https://github.com/tiann/KernelSU/actions/runs/10977394262?pr=2084 I did everything correctly. But, the problem still exists 😢  

> try this one: https://github.com/tiann/KernelSU/actions/runs/10977394262?pr=2084 bootloop with those CI builds