Chromebook bricked(?) thru gsctool after aborted command: Ctrl+D ignored in Recovery. Is CH341A flashing (WSON8) the only way?

Hi everyone,

I urgently need some advice on a tricky Chromebook issue. After an aborted gsctool command, my device is stuck in a hardware/bus deadlock. I’ve tried all standard and advanced troubleshooting steps, but without shell access, I’m currently at a dead end.

  1. Hardware & Device:
    Acer Chromebook spin cp713 2w
    (Intel platform)

stock, ChromeOS

Security Chip: Cr50 (H1)

BIOS Chip: WSON8
The current situation:

When I turn on the Cb the fan spins up briefly and then goes silent again. This happens every 10 seconds. It doesn’t boot up, nothing.

I have to boot into recovery mode, shut it down normally, and then turn it back on. Then it boots normally into ChromeOS.
Current Access Level: No access to Linux Shell / VT2 (chronos), Developer Mode is currently disabled.

  1. Root Cause & Symptoms
    Root Cause: Closed-Case Debugging unlock (gsctool -a -o) was aborted halfway through (before completing the physical presence power-button presses).

Symptoms:

No Audio: The volume slider completely disappeared from the status tray/settings.

Left USB-C Port glitching: Unresponsive / behaving erratically (just in one direction)

My recovery screen shows:

“Chrome OS is missing or corrupted. Please disconnect all connected devices and start the recovery process.”

No message like “USB stick in USB” or anything similar.

(usb recovery stick not recogniced)

Suzyqable is unresponsive. It’s completely dead.

  1. What I Have Already Tried (Unsuccessful)
    EC / AP / Hardware Reset: many debugkeys → No change.
    Powerwash: Wiped

all with and w/o battery plug.

Problem: Ctrl + D is completely ignored on the recovery screen. I cannot re-enable Developer Mode to access the shell and re-run gsctool.

  1. Questions & Next Steps
    Since the Cr50 seems stuck in a pending transaction on the SPI bus and is blocking the SMBus, I am considering:

:backhand_index_pointing_right: Flashing full UEFI firmware (e.g., MrChromebox) via a CH341A Programmer + 1.8V Level Shifter Adapter + WSON8 Pogo Pin Probe to install Windows/Linux.

My Questions:

Experience with WSON8 & Pogo Pins: Has anyone successfully flashed a WSON8 BIOS chip in-circuit using a Pogo Pin probe on a Chromebook, or does the motherboard pull too much current ?

Cr50 Behavior under UEFI/Windows: If I overwrite the main BIOS with UEFI, will the Cr50 release the SMBus/Audio + usb-c under UEFI/Windows, or will it continue to lock up the hardware?

Software Alternatives: Is there any trick to force the Cr50 to reset or trigger Developer Mode when Ctrl + D is being ignored on the recovery screen (e.g., modified USB recovery image)?

Thanks in advance for any insights!