R Why I can't login? Because of Android rollback protection. It's because your previous kernel or twrp use a security patch date higher than newly flashed kernel/twrp. Kernel and twrp also should use the same date. Here is the official documentation: https://source.android.com/security/keystore/version-binding#hal-changes What could you do to solve the problem? Different ways: - Restore your previous kernel and the problem will gone. - Use OS Patch Level changer for boot/recovery partitions https://github.com/CruelKernel/backtothefuture/releases. Flash in TWRP. You can set desired date in filename. Date format: YYYY-MM. For example: backtothefuture-2021-01.zip If there will be no date in the filename, max possible date 2127-12 will be used. If you select a wrong date, then don't reboot, rename the zipfile and flash it again. - Check the os_patch_level date of your previous kernel here https://cruelkernel.org/tools/bootimg/ and patch cruel kernel image to the same date. If your previous kernel is nemesis, patch cruel to 2099-12 date. - Reboot to TWRP, navigate to data/system and delete 3 files those names starts with 'lock'. Reboot. Login, set a new pin. To fix Samsung account activation problem, reinstall the samsung app. - Full wipe also helps.
R I can't see new kernel after flashing. Most likely you boot with kernel from recovery partition. CruelKernel has built-in magisk inside, you don't need to hold the buttons (power+volup+bixby) during booting. Maybe your rom forces booting from recovery partition. To check it try in MagiskManager > Modules > Right Corner > "Reboot to Bootloader".
Hi @SebastianSNRL / Team,
I hope you are doing well.
I am using Cruel Kernel on my Galaxy S10+ (Exynos). The kernel works very smoothly, but since Magisk v26.3 is hardcoded into the kernel, I am having issues updating Magisk or using Zygisk and modern modules (like Play Integrity Fix) to pass device certification.
Could you please release a minor update for the S10+ kernel build with the latest Magisk version integrated? Or is there an officially recommended way to manually patch the boot image without causing a bootloop?
Thank you for your great work on this kernel!
R Is it possible to update magisk or install canary? No, it's not possible to update magisk without installing new kernel version. Built-in kernel magisk is not updatable. You can wait for new kernel release, or build the kernel on github. GitHub fetches latest magisk version available on https://github.com/topjohnwu/Magisk/releases page during build. You can rebuild the kernel with canary magisk, just use +magisk=canary instead of +magisk in main.yml You also can specify different versions of magisk with +magisk=20.4 or +magisk=21