Can REA help analyze Android firmware, bootloaders, and device trees for custom ROM development?

[amitpadhan525]

I'm interested in learning how Android firmware works at a deeper level, especially bootloader images, device trees (DTB/DTBO), vendor boot images, and verbose boot logs.

Can REA help extract and analyze these components from a stock firmware package? Also, is it possible to identify missing device tree sources or understand boot failures from kernel logs when working on custom ROMs?

[ChangkeunJ]

Partly. Firmware input is capped at 128 MiB, so unpack the package yourself and feed single images (boot, vendor_boot, dtbo) to inspect_firmware_regions and extract_firmware (your binwalk and unblob). Extracted ELFs open in Ghidra via open_binary, and so does a headerless bootloader with format raw-binary, arm64 and an entry point. inspect_devicetree (6.8.0) takes one bare FDT blob, so split a dtbo.img first; no .dts, no overlays. Kernel logs aren't analysed; adb logging needs a booted device.