The workflow that's documented in the wiki is for users to boot from the "box" image (which contains autoscript files that should hook vendor u-boot) then download a device-specific image to eMMC to /storage and write using emmctool. It's also possible to create a combined .img file that has mainline u-boot + extlinux + autoscript boot files to handle users who see 'mibox4' in the image filename and attempt to use that first. It works because vendor u-boot ignores the extlinux files and mainline u-boot ignores the autoscript files. The combined .img type is what the buildsystem creates by default when the amlogic-boot-fip device name e.g. 'mibox4' falls-through the case statement in projects/Amlogic/bootloader/mkimage. Does the "box" image boot from USB once a device-tree dtb has been added to the /amlogic folder?
For testing you can add WiFi/BT firmware locally https://wiki.libreelec.tv/how-to/add-firmware - You can also hack files into the image using projects/Amlogic/filesystem/usr/lib/firmware/xxx - not something I'll accept in our main repo but fine to save effort during development.
NB: It would be easier to review things if you cloned https://github.com/LibreELEC/LibreELEC.tv and pushed a topic branch with the changes. Same for https://github.com/torvalds/linux and https://github.com/u-boot/u-boot respectively.