OpenWRT on Philips Hue Bridge, probably brick

Hi, I recently bought a Philips Hue Bridge 2.1 from an auction site. Received it today and the does not work, only one LED is On when connected to power. Started browsing the internet, changing the ethernet cable, ports did not help, the reset button did nothing. Decided to solder pins to the board plug it into the UART, connected via putty and this is the result.

U-Boot 1.1.4 (Jun 23 2020 - 07:52:07)
 
bsb002 - Honey Bee 2.0DRAM:
sri
Honey Bee 2.0
ath_ddr_initial_config(195): (16bit) ddr2 init
ath_sys_frequency: cpu 650 ddr 597 ahb 216
DDR_CONFIG  = E7AAF33B
DDR_REFRESH = 40C3
tap = 0x00000003
Tap (low, high) = (0xa, 0x24)
Tap values = (0x17, 0x17, 0x17, 0x17)
64 MB
Top of RAM usable for U-Boot at: 84000000
Reserving 215k for U-Boot at: 83fc8000
Reserving 192k for malloc() at: 83f98000
Reserving 44 Bytes for Board Info at: 83f97fd4
Reserving 36 Bytes for Global Data at: 83f97fb0
Reserving 128k for boot params() at: 83f77fb0
Stack Pointer at: 83f77f98
Now running in RAM - U-Boot at: 83fc8000
Flash Manuf Id 0xef, DeviceId0 0x30, DeviceId1 0x13
flash size 0MB, sector count = 8
Flash: 512 kB
Power up PLL with outdiv = 0 then switch to 3
*** Warning *** : PCIe WLAN Module not found !!!
In:    serial
Out:   serial
Err:   serial
Net:   ath_gmac_enet_initialize...
Fetching MAC Address from 0xXXXXXX
No valid address in Flash. Using fixed address
ath_gmac_enet_initialize: reset mask:c02200
Honey Bee ---->S27 PHY*
S27 reg init
: cfg1 0x800c0000 cfg2 0x7114
eth0: XX:XX:XX:XX:XX:XX
athrs27_phy_setup ATHR_PHY_CONTROL 4 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 4 :10
eth0 up
Honey Bee ---->  MAC 1 S27 PHY *
S27 reg init
ATHRS27: resetting s27
ATHRS27: s27 reset done
: cfg1 0x800c0000 cfg2 0x7214
eth1: XX:XX:XX:XX:XX:XX
athrs27_phy_setup ATHR_PHY_CONTROL 0 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 0 :10
athrs27_phy_setup ATHR_PHY_CONTROL 1 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 1 :10
athrs27_phy_setup ATHR_PHY_CONTROL 2 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 2 :10
athrs27_phy_setup ATHR_PHY_CONTROL 3 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 3 :10
eth1 up
eth0, eth1
Qualcomm Atheros SPI NAND Driver, Version 0.1 (c) 2014  Qualcomm Atheros Inc.
====== NAND Parameters ======
sc = 0x83ff7040 page = 0x800 block = 0x20000
Setting 0x181162c0 to 0x4081a100
Hit any key to stop autoboot:  0
 
Loading from device 0: ath-spi-nand (offset 0x2c00000)
   Image Name:   MIPS OpenWrt Linux-4.4.60
   Created:      2021-09-24  18:37:03 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1533630 Bytes =  1.5 MB
   Load Address: 80060000
   Entry Point:  80060000
## Booting image at 81000000 ...
   Image Name:   MIPS OpenWrt Linux-4.4.60
   Created:      2021-09-24  18:37:03 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1533630 Bytes =  1.5 MB
   Load Address: 80060000
   Entry Point:  80060000
   Verifying Checksum at 0x81000040 ...Bad Data CRC
ath>

Suposes the bridge is a brick, can anyone know how to unbrick it.

Thanks for help

This device is not supported by OpenWrt, so it's probably running some vendor fork, thus asking on this forum is not the best action. Anyway, I'll assume someone wanted to port it to official OpenWrt and failed, leaving device in broken state.
Judging from FCC photos the Hub has two flash chips, one NOR SPI and one NAND SPI. Bootloader seem to be placed in NOR flash while the rest is in NAND. Bootloader doesn't seem to report any bad blocks on NAND flash, but taking failed CRC check of kernel image into account, that is very likely the problem. The second possibility would be broken/interrupted update, which could result in failed boot. In both cases You'll need firmware copy to recover and writing it to NAND flash. Might be that vendor implemented some kind of fallback for failed firmware write (very unlikely since it fails anyway), so checking U-Boot environment and help output could give some clues. Check this blog post: https://blog.kleine-koenig.org/ukl/philips-hue-bridge-v21.html how to access U-Boot command line. Maybe @ukleinek has more to say about the device, since that's his site.
Good luck.