[ifoknr]

Samsung flashing (Odin protocol, as Heimdall sends it)

• In the Download mode window, after a reading: Flash… takes one image (.img, .lz4), a Magisk tar, or the whole firmware (BL, AP, CP, CSC/HOME_CSC).
• Before anything is sent: each .tar.md5 against its MD5 line, each LZ4 image decoded once (size and checksums), every file matched to the phone's PIT and the firmware's model to the phone's.
• Refused: EFS and the other identity partitions, a PIT (no repartitioning), firmware for another model, files bigger than their partition, two files for one partition, CSC with HOME_CSC. Warnings (bootloader or modem alone, CSC or userdata wipe, mixed builds, unknown model) must be ticked as read before Flash turns on.
• The flash itself: 1 MiB parts when the bootloader offers them, the total size first, then the PIT read again: a different phone gets nothing written. After a failure the session ends without a restart, so the phone stays in Download mode.
• Core: OdinClient.PrepareTransfers/SendTotalBytes/FlashFile, OdinSources, OdinFlashPlan, OdinFlasher; the stand-in phone takes flashes; 20 new tests (one uses Samsung's own AP fixture).

Google USB driver

• Settings has a USB drivers card (Google and Samsung). The USB check offers Google's driver for a phone on Google's USB id.
• Downloaded from dl.google.com, kept only when size and SHA-1 match Google's SDK catalogue (r13 pinned by SHA-256), unpacked, and added with pnputil /add-driver … /install, which asks for permission and checks Microsoft's signature on the driver.

Also: help (Settings, Samsung), README, CI screenshots of the plan and of a flash to the stand-in phone, v2.9.0 notes in both languages. No release.