Current slot
The slot selected for the next boot attempt. It can still be unsuccessful or even become unbootable.
ANDROID FIRMWARE / SUPER / A-B / VERIFIED BOOT
Understand the image
Understand the image
before you flash it.
Trace boot verification, A/B slot state, dynamic-super metadata, image format and flash interface before making destructive changes.
FIRMWARE BOOT / FLASH PATH
BOOTLOADERLock / slot
AVBvbmeta chain
SLOT_a / _b
SUPERLP metadata
FILESYSTEMEROFS / EXT4
ANDROIDMount / init
A successful flash command does not prove the image, slot, metadata and verification chain are mutually compatible.
FIRMWARE INTELLIGENCE FINDER
OPEN FIRMWARE FINDER →Open reviewed package evidence
Search analyzed firmware records with GPT/LUN, A/B, AVB, storage and hazard evidence. Compatibility remains NOT_PROVEN until device evidence supports it.
01 — THREE FIRMWARE DOMAINS
AVB, Dynamic Super and A/B are different systems
The uploaded V1 already separates these domains. V2 keeps the same architecture and adds safer decision logic.
02 — FIRMWARE / VERIFICATION HIGHWAY
Click each stage to inspect what it verifies, what it depends on, and what a failure at that stage really means.
03 — FIRMWARE FAILURE PROFILER
Symptom → state → partition → confirmation
Failure cases are adapted from the uploaded source, but V2 avoids generating one-size-fits-all destructive commands.
SELECTED FIRMWARE CASE
Observed evidence
Likely domain
Confirmation tests
BOOT / VERIFICATION PROGRESS
04 — MASTER PARTITION / AVB SCHEMA
Know what each image actually belongs to
Search physical partitions, logical partitions, AVB descriptors, slot architecture and preferred flashing context.
| Partition / Layer | Container | Verification | Slot Architecture | Typical Interface | Failure Impact |
|---|
05 — LIVE FIRMWARE EVALUATOR
Build a repair route from actual state
Enter slot, lock, bootability, Fastboot/Fastbootd, AVB and super-image evidence before choosing a repair action.
06 — A/B SLOT INTELLIGENCE
Bootable, successful and active are not the same thing
Use slot metadata and retry counters as state evidence. Exact retry defaults and implementation details can vary by bootloader/device.
Allowed to boot
A bootloader attribute indicating whether the slot can be attempted.
Marked good
A slot becomes successful only after the platform's boot-control logic commits that state.
Remaining attempts
Used by A/B boot-control logic. Do not assume a universal fixed maximum for every vendor implementation.
07 — DYNAMIC SUPER / IMAGE FORMAT
Metadata, group sizes and filesystem format all matter
Separate logical-partition allocation failures from sparse/raw transfer issues and filesystem rebuild problems.
Metadata slots / block size
Defines the dynamic-partition container geometry and metadata copies.
Logical size pool
system, product, vendor and other logical partitions must fit the configured group size.
Physical block mapping
Logical partitions are mapped to extents inside super rather than fixed GPT partitions.
Filesystem image
Image rebuild and resize behavior depends on the actual filesystem format. Do not treat EROFS like writable EXT4.
Transport format
Sparse Android images and raw images are different representations; tool support and size limits vary.
Userspace logical operations
Many dynamic-partition operations are performed in Fastbootd, but exact flash support varies by device/bootloader.