When you say "bricking", you mean not destroying it due to some HW mishap, but a software issue that prevents it from booting?
I have a few 1000 Omega2S out in the field and so far only ever had to software-level unbrick one (I actually burnt a few more due to PSU issues in one production charge, and soldering parameter errors in another, but these are different stories).
From that one I learnt that all you need to unbrick from any level of software brick, including ruined u-boot (which IMHO can't be repaired in the devkit) is
a way to apply power only to VDD_FLASH (A7) but not to the other VDD pins (C17, C18), to activate the SPI flash chip but not the MT7688 SoC (nor any other part of your circuitry)
access to the SPI lines (A8..A12)
a SPI flash programmer (anything from cheap $3 aliexpress up to Segger - in my case, a colleague had the latter and knew how to use it)
Only the first bullet point might be difficult (but usually manageable by cutting some tracks) if your PCB design does not provide for it. Accessing A8..A12 should always be possible; if you have to do it more than once, building an apdapter with 6 pogo-pins helps a lot.
With such a setup, you can write every single byte of the SPI flash chip inside the Omega2S, and with that, reflash any part of it that might be bricked.
That way, you don't need to unsolder the Omega2S completely to unbrick it
PS: if you can pull up GPIO38, have Ethernet and the serial console, and not bricked u-boot, but only openwrt, then unbricking is even simpler via the built-in recovery http server, see docs.
