Add a setting for usage of sha1 from ramdisk

[RimuruChan]

Apologies for any inconvenience. I'm curious about why we prefer to perform a check and use the SHA1 of a CPIO file instead of simply calculating the SHA1 of the partition itself?

KernelFlasher/app/src/main/java/com/github/capntrips/kernelflasher/ui/screens/slot/SlotViewModel.kt

Lines 115 to 125 in 1cbbba4

	if (ramdisk.exists()) {
	when (Shell.cmd("$magiskboot cpio ramdisk.cpio test").exec().code) {
	0 -> _sha1 = Shell.cmd("$magiskboot sha1 $boot").exec().out.firstOrNull()
	1 -> _sha1 = Shell.cmd("$magiskboot cpio ramdisk.cpio sha1").exec().out.firstOrNull()
	else -> log(context, "Invalid ramdisk in boot.img", shouldThrow = true)
	}
	} else if (kernel.exists()) {
	_sha1 = Shell.cmd("$magiskboot sha1 $boot").exec().out.firstOrNull()
	} else {
	log(context, "Invalid boot.img, no ramdisk or kernel found", shouldThrow = true)
	}

[capntrips]

The original idea was to keep up with the original boot image to avoid bootloops. The available backups are also tied to that value. A change to that functionality has been requested on XDA, as well. I plan to add toggles for both features on a settings screen, but I wouldn't expect it in the coming weeks.