Safety
A finished write cannot be cancelled.
Flashing, unlocking, relocking, root changes, partition writes, and restores can erase data or leave a device unable to boot.
What the app does
- Freezes the plan, including the target and the hashes of the inputs that matter.
- Rechecks those inputs before it runs.
- Asks for a typed confirmation on destructive work, tied to that device.
- Keeps interrupted operations for inspection, and does not replay them.
- Refuses incremental OTAs instead of guessing.
What that does not prove
- The image is authentic, compatible, or safe against anti-rollback.
- The phone will boot when the command returns.
- A restore plan that matches device, build, slot, and content will actually boot.
- A root script for a pinned provider version has been run on hardware.
- This preview behaves like upstream PixelFlasher.
Development does not flash, root, unlock, relock, wipe, pair wirelessly, or restore anything on hardware. The confirmation is a safeguard, not a guarantee. More detail is in validation and architecture.