Extracting Boot Images on DC-1 🧰

If you're looking to modify your boot image or create a custom kernel setup on the DC-1, you'll need access to the boot partition. This guide walks you through extracting the correct boot image using Termux (opens in a new tab) with Superuser already installed and working. 🧑‍💻

Root Access via Termux ⚡

Open Termux, then type the following command to enter a root shell:

su

When prompted, approve the superuser request. You should now have full root access to the system.

Find Your Boot Partition 📍

Once you’ve got root access, run this command to locate the boot partition(s):

for PARTITION in "boot" "boot_a" "boot_b"; do
  BLOCK=$(find /dev/block \( -type b -o -type c -o -type l \) -iname "$PARTITION" -print -quit 2>/dev/null)
  if [ -n "$BLOCK" ]; then
    echo "$PARTITION" = $(readlink -f "$BLOCK")
  fi
done

This will print paths like:

boot_a = /dev/block/sda40  
boot_b = /dev/block/sda41

A/B Devices: Know Your Slot 🧠

If you see both boot_a and boot_b, your device uses A/B partitioning. To find the active slot, run:

getprop ro.boot.slot_suffix

• If the result is _a, you'll want boot_a
• If it's _b, use boot_b

If only a single boot partition is returned, your device uses a standard A-only layout—easy.

Extract the Boot Image 🗃️

Once you know the correct boot partition path, extract it with:

dd if=<boot_partition_path> of=/sdcard/boot.img

Example:

dd if=/dev/block/mmcblk0p42 of=/sdcard/boot_a.img

This creates a copy of the boot image in your internal storage, ready for patching, backup, or further reverse engineering. 🛠️

Next Steps 🚀

Now that you’ve got your boot image, you’re ready to:

• Patch it with Magisk or another root solution
• Modify it for kernel dev
• Flash it back with fastboot flash or your preferred recovery method

If you run into issues or need help patching or repacking boot images, hop into our Discord (opens in a new tab) and ask! 💬