Skip to content

Instantly share code, notes, and snippets.

View amotrak's full-sized avatar

dmыtro amotrak

  • Ukraine
  • 12:52 (UTC +02:00)
View GitHub Profile
@amotrak
amotrak / comfast_cf-wr632ax_unbrick.md
Created February 14, 2026 13:40
comfast cf-wr632ax U-Boot layout unbrick

For those who have already switched to the U-Boot layout and wanted to go back to the stock bootloader:

Prerequisites:

Here is the photos when the top case is removed: https://openwrt.org/toh/comfast/cf-wr632ax#photos

  1. Remove the top case of the router and solder UART (I have a cp210x usb to UART bridge)
  2. Get mt7981-ram-ddr3-bl2.bin and openwrt-mediatek-filogic-comfast_cf-wr632ax-ubootmod-bl31-uboot.fip from the andros-ua repo to boot them using mtk_uartboot
  3. Get the latest snapshot of *initramfs-recovery.itb from the OpenWrt firmware selector
  4. Rename *initramfs-recovery.itb to openwrt-mediatek-filogic-comfast_cf-wr632ax-ubootmod-initramfs-recovery.itb and serve on TFTP (/srv/tftp on Arch, use TFTPD64 on Windows)
@amotrak
amotrak / comfast_cf-wr632ax_unbrick
Last active February 14, 2026 11:46
COMFAST CF-WR632AX U-Boot layout unbrick
**TLDR**: U-boot layout is currently broken for both the snapshot and RC1-RC4 preloader & FIP
**DO NOT** flash preloader and FIP from the latest "U-Boot layout" snapshot from the OpenWrt firmware selector, it's broken and you will get yourself softlocked with the only one possible way to recover: boot working preloader (BL2) and U-Boot (FIP) using ![mtk_uartboot](). However, the only preloader and FIP which is possible to boot this way is ![working](), other release candidate versions from firmware selector don't work. Use Windows for mentioned unbricking method, on Arch I had no success and every time I had the following message: **Waiting for BL2. Message below: Timeout waiting for specified message.**
The second issue with U-Boot layout occurs with RC1-RC4 preloader & FIP -- even though it boots successfully, I've got random kernel panic crashes (see logs below) supposedly upon some time after enabling WI-FI which then lead to reboot into recovery image.
For those who have already switched to U-Boot lay