M30 Kernel Diff
One traceable image.ANDROID · LINUX · RFCOMM
Research is stronger when the path from source to device is traceable.
This repository records five ordered source patches and the effective configuration for an RFCOMM-enabled Galaxy M30 research kernel, flashed to my own phone on 31 October 2026. It ties source, image, boot artifact, and post-flash readback with SHA-256 hashes. Android booted with SELinux Enforcing; root, Wi-Fi, Android Bluetooth, Linux hci0, and RFCOMM/L2CAP protocol registration were checked. A phone-side RFCOMM socket exchange with the cooperating laptop was not tested on this image.
Five patches, in order.
The source record contains five patches applied in a defined sequence and a cumulative four-file change, making the research image auditable.
Provenance all the way down.
Recorded kernel configuration and SHA-256 hashes connect the published source state to the patched image, BOOT artifact, and exact post-flash readback.
Say exactly what worked.
The phone booted; SELinux remained Enforcing; Android and Linux Bluetooth paths were present and RFCOMM/L2CAP registered. The remaining phone-side RFCOMM socket exchange is explicitly untested.
