# Recovery features via a USB port

**URL:** <https://community.frame.work/t/recovery-features-via-a-usb-port/46359>\
**Category:** Framework Laptop 16\
**Tags:** framework-laptop-16-amd-7040\
**Created:** [March 3, 2024, 11:26pm UTC](https://community.frame.work/t/recovery-features-via-a-usb-port/46359 "2024-03-03T23:26:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![MJ1](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mj1/32/15519_2.png) [@MJ1](https://community.frame.work/u/MJ1)\
**Post date:** [March 4, 2024, 12:02am UTC](https://community.frame.work/t/recovery-features-via-a-usb-port/46359/2 "2024-03-04T00:02:57Z")

</div>

Given how easy Framework are to open, not sure if we need this via a USB port. Mobile phones need it due to most being glued shut these days.

But a reflashing header on the FW16 mainboard would be great. At least for the FW13, there isn’t one. It has an EC debug header on the mainboard, and even via a USB port. [howett.net/posts/2023-04-framework-ec-card](https://www.howett.net/posts/2023-04-framework-ec-card/). No reflashing through these, though. To recover a faulty flash, you need to use a flash programmer and pogo pin adapter on the chip. [community.frame.work/t/how-to-prepare-for-reflashing-firmware/31001](http://community.frame.work/t/how-to-prepare-for-reflashing-firmware/31001). So yeah, just a header would be a big step up.

---

_[View the full topic](https://community.frame.work/t/recovery-features-via-a-usb-port/46359)._