FHam

@FHam,
 
I wish you best of luck in getting this working.  It is possible (maybe?), however can be difficult (as you are perhaps finding out).
 
If you cannot get it working, or get tired of messing around with unsupported devices, you could also consider starting over with one of Armbian officially supported devices, where you would not only have a much easier time, but also enjoy long term and (generally) much more stable support situation.
 
Just something to consider.  I really feel bad for you guys struggling with these TV Boxes in here.  But the wide variations and random hardware make them extremely difficult to support.  And without software support, the most impressive specs in the world "on paper" really don't mean anything.
 
By contrast, I am enjoying a couple well supported devices for a number of years now, they run flawless and for the most part "just work."  Just keep it in mind, the next time you go device shopping...

@FHam 
First I want to restate some of the basics around armbian on android tv boxes.  1) They are not supported.  2) A single developer (balbes150) has worked years on getting things to the state they are.  3) As of October 14th balbes150 removed support for amlog cpus, so that is the last build that will maybe work on your box, 4) There is a very small number of people on this forum/club that are able to provide any guidance, 5) Most likely no one on this forum/club has ever seen your specific box, 6) Expectations should be set low (i.e. don't expect anything to work) but if you do get the box to boot, get hdmi and wired ethernet to work, you are doing good.  7) Really don't expect things like wifi, bluetooth, remote control etc to work.  8) If you get this working on your box, it will likely only be useful for server type tasks, maybe a little light graphical desktop usage, but certainly not video/multimedia.
 
There is a lot of information in the two threads you have opened on your installation problems.  I think at this point it would make sense to start from the beginning and step through the basics to try to help you.  There were a couple of very important questions asked of you in the old closed thread that you didn't answer.  I am going to make some recommendations in an effort to try to help.
1) Use the latest/last build that supports amlogic cpus: https://yadi.sk/d/_rQgn_FosYuW0g/20.10/20201014
2) Follow the instructions (I agree that the instructions are often not clear) from the first post of this thread: 
I recently wrote a post that attempted to help someone better understand the instructions for an amlogic cpu as he was having difficulty understanding the instructions from balbes150.  This may help you:
 
 
 
3) Pay particular attention to the first sentence in red.  If you have ever tried to install other linux builds on this box, stop.  You will first need to restore the box with an original android firmware before continuing.  This is true even if the box is still running android.  The key here is if you have ever 'attempted' to install something else.  The installation process for some other firmwares will modify the booting environment in ways that cause the armbian install to no longer work.  The armbiantv installation is dependent on an unmodified default android environment.  I have more than once solved problems I have had by reverting a box to a clean fresh state by reinstalling the android firmware.  Note, when I say reinstall the android firmware, that doesn't mean using the android functionality to reset the box, it means going out and finding the correct manufactures firmware file and using the low level amlogic tools to install that on your box.  This is one of the questions asked in the previous thread that you didn't answer, which is why I am spending so much time on it.  It is critical that the state of the box be known and clean otherwise we are all just wasting time.
 
4) In your previous thread you have a screen shot showing you trying to run aml_autoscript.zip from android recovery.  From my understanding if you find yourself in android recovery you are doing something wrong.  No part of the installation process uses android recovery.  I have always been successful with the 'toothpick' method and would recommend you stick with that.  
 
5)  The extlinux.conf file you posted in the previous thread had a number of errors in it.  Please post the extlinux.conf file you are currently trying to use.
 
You are working with a box that isn't common.  I have no experience with it.  But by correctly following the installation, you may yet be successful. 

Thank You "TRS-80", I appreciate your response. 
 

Thanks Tido, Seriously, I wish I was kidding.  I have already followed the steps prior to your message.  and I get the same error regardless of the dtb file I use.  I have renamed and tried both u-boot-s905x-s912 and the s922 --> renamed to u-boot.ext
 
See the screen capture below.  Note I have even tried copying the files and renaming it to dtb.img and I get the same crappy error message.  The 1st screen capture shows the use of the "meson-gxl-s905x-p212.dtb" which btw like all makes no difference.