Here's the backup: https://mega.nz/file/MBV0FbjC#SFhkL9yvnxsE9EKuwhJBSX2J_cGom3HQbZrwg1FjmdM
I'm not sure if the literal first 32 bytes of the extracted file is significant, but if it actually is, for convenience, here's the hex dump for the first 32 bytes:
00 01 83 00 00 02 00 00 00 00 00 00 00 00 00 00 16 00 00 00 00 00 00 00 64 06 00 00 00 00 00 00
To my surprise, when I booted the second board up just now, it detects the esp8089 and even lists it at ifconfig as wlan0... And after a few reboots (probably 2 or 3) and switching between crystal_26M_en values, now it doesn't... It randomly works on 26M regardless if set as 1 or 0
At that time that it was working though, I still can't connect with it for some reason (using armbian-config), and ifconfig lists the wlan0 interface as an "Ethernet" device, + yeah the LEDs are still acting weirdly
This is all using the led-conf5 option btw, which, shows `working` and `auxiliary` for `/sys/class/leds` but uses it as if it's just one LED and switches between red/blue, instead of being 2 individually controllable LEDs, and apparently its default trigger is mmc2 activity
I haven't set it up on my network yet to copy/paste dmesg as that would require me to set a static IP for it and place it far away from my workdesk, and near the router as only the ethernet works... but here's a photo of dmesg, grepping through possibly relevant keywords: https://imgur.com/a/VjpJUkr
Thanks for your time!