Wizzard

@Wizzard  The boot environment is stored on emmc.  So when you boot (enable multiboot via holding the reset button) that is setting certain variables in the u-boot environment and persisting them there (which is on emmc).  That is why you only need to press the reset button the first time you boot Armbian or any other distribution.  But the way that the distributions setup the boot environment are different (and usually not compatible) - even the Armbian legacy stuff from balbes150 changed how it was done (in incompatible ways) a number of times over the years.
 
So without knowing what has been changed in the u-boot environment that is stored on emmc, it is impossible to really support people.  So there is a check in the Armbian code that looks for certain changes that indicate something else has run and then fails the boot.
 
 

Github https://github.com/armbian/community/releases

Which dtb are you using?
 
Since you found someone who apparently got these things working, you would probably be best served by reaching out to them to see what they did to get wifi/sound working on this box.  It looks like they forked their build from armbian a while back and here is a link to the diff between the base armbian they forked from and their set of changes: https://github.com/armbian/build/compare  (Your answers are somewhere in that diff).  Since I don't own that box, there isn't much I can do beyond pointing you in these directions.

@Wizzard In searching through this thread and the forums, I can't see anyone reporting to have tried installing on your model.  Since no one has responded to your post, it is unlikely anyone around here has your model of box and therefore unlikely to be able to help you out.  There are hundreds of different TV box models each with different components which makes support for the vast majority nearly impossible.  There is likely information in this thread that could help you, but unfortunately you are likely on your own to sort through it and try out potential solutions to get your box working.  One thing I noticed in this thread that may be helpful to your case is a comment that mentioned replacing the uboot on the armbian image with a libreelec uboot.  Since you indicate you can boot libreelec that path sounded relevant to your situation.  Unfortuantely I don't own any rockchip boxes and therefore am of little help beyond providing pointers to others efforts.

Resolution:
 
to add this line to /boot/armbianEnv.txt
 
extraargs="video=1280x720@60"
 

Hello Everyone, I would like to share my experience about how to boot Orange Pi almost silently in console mode (eliminate a lot of kernel messages on startup) without desktop and remove cursor blinking that can cause black rectangle appearing over white background, when painting to framebuffer. Many options that proposed as being able to reduce kernel messages on boot didn't work for me. So based on Armbian documentation I started to experience with armbianEnv.txt file in the /boot folder. The extraargs setting was not part of the default armbianEnv.txt file, but appeared in BOOT.CMD file. The setting
 
extraargs=vt.global_cursor_default=0 quiet
 
solved both above problems. Hope this will be helpful for somebody else.

Aight, will do. I'll edit here once its finished.
 
https://werner.armbian.de/_extra/Armbian_20.08.0-trunk_Bananapi_focal_current_5.7.16.img.xz

I do not have this board so I cannot test that.
I create a new image with generic joystick support and added all available models as modules. Let me know if it works.
 
https://werner.armbian.de/_extra/Armbian_20.08.0-trunk_Orangepipc_focal_current_5.7.16.img.gz
 

Did a quick check. xpad module seems to be missing in sunxi kernel configs while it is present in rk* und some other. I'll look into

I must say I am very satisfied with Armbian. Using it as my primary OS now. Just the graphics acceleration is not perfect yet (Retroarch, PP Racer etc.), but it is really usable. Keep on good work!