# FriiDump Candidate18: Windows Sequence Parity

Candidate17 is rejected and must not be tested or promoted. It incorrectly generalized `RecoveryKick` from an experimental modified GDR-8050L 0012 firmware path.

Candidate18 returns to Candidate16 and ports the proven Windows state-aware sequence into the portable Linux path:

1. `EnsureDriveReady(30000)`;
2. entry `READ CAPACITY`;
3. if already in game view, skip redundant handshake and tray cycle;
4. otherwise run `UnlockDrive()` directly;
5. `RefreshVolume()`, 2000 ms settle, readiness, and capacity observation;
6. only when still in video view, perform one tray cycle and repeat the handshake plus refresh/readiness/capacity sequence;
7. fail if the game view is still not established;
8. request maximum speed;
9. acquire the volume lock where supported and probe metadata.

The same state-aware helper is used after visible-video capture to re-establish the game view. Generic `RecoveryKick`, repeated LBA-zero reads, and automatic media-auth kicks are removed from both portable and copied Windows dump paths. Experimental modified-firmware recovery remains out of scope.