Skip to content

Commit 80e0cc9

Browse files
Fix No Ramdisk found issue. (#6)
This fixes the issue for Samsung devices like Samsung S24 devices and other devices with init_boot but single slot. shell: su -c ls -la /dev/block/bootdevice/by-name/init_boot* < lrwxrwxrwx 1 root root 16 1970-12-19 22:58 /dev/block/bootdevice/by-name/init_boot -> /dev/block/sda28 shell: su -c ls -la /dev/block/bootdevice/by-name/boot* < lrwxrwxrwx 1 root root 16 1970-12-19 22:58 /dev/block/bootdevice/by-name/boot -> /dev/block/sda27 Also for devices with Ramdisk in Vendor boot like Pixel 6 series.
1 parent ac6360f commit 80e0cc9

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

anykernel.sh

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -44,11 +44,11 @@ ui_print " " " -> ksu_supported: $ksu_supported"
4444
$ksu_supported || abort " -> Non-GKI device, abort."
4545

4646
# boot install
47-
if [ -L "/dev/block/bootdevice/by-name/init_boot_a" -o -L "/dev/block/by-name/init_boot_a" ]; then
48-
split_boot # for devices with init_boot ramdisk
49-
flash_boot # for devices with init_boot ramdisk
47+
split_boot
48+
if [ -f "split_img/ramdisk.cpio" ]; then
49+
unpack_ramdisk
50+
write_boot
5051
else
51-
dump_boot # use split_boot to skip ramdisk unpack, e.g. for devices with init_boot ramdisk
52-
write_boot # use flash_boot to skip ramdisk repack, e.g. for devices with init_boot ramdisk
52+
flash_boot
5353
fi
5454
## end boot install

0 commit comments

Comments
 (0)