SteeMan

Are you following the instructions in the FAQ: https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus
 

@jhg If you really want to dig into this more, you would need to hook up to the colsole interface on your box.  To do this you would need to identify the console connector location on the board, solder a connector to it and then get a usb adapter to monitor the low level u-boot output.  The first stages of uboot output to the console only, then the chain loaded uboot (uboot.ext) will display stuff at later stages to hdmi.

@jhg  FYI the s905x3 cpu should be using a meson-sm1-* dtb.   sm1 is the internal code for the x3 (glx is the s905 and g12 is the x2 family).  So I would recommend starting to test with:  meson-sm1-sei610.dtb
 

@Sameer9793  The TV Box environment for amlogic and rockchip is very different.  In these forums there are two threads that cover a lot of the rockchip varients (https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes and https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards)
@jock and @fabiobassa are the two experts in that area in the forum.

Then the short answer is there isn't source for these no longer supported (technically never supported as TV Boxes have never been officially supported) builds.
However, you seem to have sufficient technical skills and therefore I will point you down the path of building your own kernel (and thus you will have everything you need).  Review the following thread: https://forum.armbian.com/topic/9625-compiling-and-booting-mainline-linux-for-your-s9xxx-tv-box
That is where I began my journey with armbian on amlogic TV Boxes.  I think everything in that thread, (mostly thinking about my post with instructions) is still valid, although I have moved on to doing things differently now days.  But I am running latest verisions of 5.4LTS, 5.10LTS and even 5.15.rc on various TV Boxes as I write this.  So if you have the proper skills, you are not stuck with the kernel you currently have running.

Please read the following FAQ item from the TV Box forum:
https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
 

Sorry for my late reply, but looks forum not allow me to post more once per day.
And Yes, you are right! I also found this step, and now latest armbian on this box :).
I burn multitool to both sdcard and USB Stick, so it can boot. Booting from USB stick, but then works with sdcard (resize partition and search img files in images dir)
About pictures, it is below:
ROM - 16G eMMC Samsung KLMAG2WEMB-B031
RAM - 4x4Gb DDR3 Samsung K4B4G0446B-HYK0
WiFi - SV6051P
 

@ballerburg9005 I just wanted to add a few of my own thoughts to this thread.  Overall I can see both sides to the above discussion.  There are valid points made by everyone commenting.  While we all sometimes need to have 'grand visions' of the future we would like to work towards, we also have to deal with the reality of where we currently are.  I often think of a saying "crawl, walk, run".  While we all want to be running to the finish line of an Olympic race, we all start by crawling first.  As that relates to armbian and more specifically armbian on TV boxes, we are at the crawling stage.  There is a lot of work to be done to just get us walking.  That doesn't mean that crawling and walking in themselves aren't valid and productive stages (they are and you can use a lot of different TV boxes today to do a lot of productive stuff).
There is a lot of work to be done today to improve our crawling.  We need volunteers (like you) to pick up that work if we ever hope to get further along our path.  We need to build a community one volunteer at a time.  While visions are important, if we don't have people willing to do work today then we will never more forward.
If you hang around armbian for any extended period of time, you will learn that the single thing that most bothers the core maintainers of the project are people having grand visions or even small visions of what should be done but who don't contribute any time to help and expect others to do the work for them.
Whether intentional or not, that is how your post came across to Igor and Balbes and they reacted as they normally do to such posts.
If you want to run to the finish line with your vision, you need to start by crawling.  Spend time on these forums following the issues to build your knowledge.  Help support new users to allow others with the technical knowledge time to work on development and progress on our shared goals.  This all doesn't happen overnight.
I welcome your contributions to the efforts here, but starting off by getting into a disagreement with two of the core maintainers isn't likely the best way to have started.  Overtime you will realize we all share a lot of the same goals and can work together even through we have different personalities and sometimes have to overcome language/cultural differences.

@giga What armbian tv box builds have you tried?  What instructions have you tried? What dtb's have you tried?  I don't have this box but have armbian running on a different rk3399 based box.

@Wester_Minskno, you misread the datasheet.
Each chip is 2gbit, you have 8, then it's 16gbit / 8 = 2 gbyte, no way out. The specs given by the manufacturer are fake.

@Jason Duhamell  Please don't post large files inline.  Use the "Spoiler" feature to hide long attachments (the icon that looks like an eyeball).  It makes it much easier to read these threads without having to scroll through large files.

@Crypto_Dino I'm not sure which instructions you are following, but you aren't using the correct latest builds for the h6, nor following instructions correctly.  The latest builds by balbes150 for the Allwinner H6 are located here:  https://users.armbian.com/balbes150/aw-h6-tv/
As for instructions you mention renaming files to u-boot.ext.  That is an instruction for Amlogic CPUs not the Allwinner H6.

@zhuceluntan Please read the following FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
As is indicated there balbes is no longer involved in supporting Amlogic s905x cpu based boxes. 
Please do not direct posts directly to a specific user as that is a bad practice.  That sends the message the you are expecting a specific volunteer to provide you support and that runs counter to the Armbian community support model.  Volunteers help the project in the ways they can, and may use their time to answer the posts they feel they have time to.  Obviously if you are engaged in a conversation with a specific person in a thread it is fine to tag them, but to log a new post tagged to a specific person is not good form.

These instructions are for Amlogic CPUs for TV Boxes. 
 
Note: If you have previously run other distributions on the box such as coreelec the below installation will not work.  You will need to restore the original android firmware before attempting the install.  coreelec changes the boot environment in ways that are incompatible with these Armbian builds.
 
Download links:
    Weekly Community Rolling Builds:  https://www.armbian.com/amlogic-s9xx-tv-box/
    or build your own image using the Armbian build framework
 
Once you download your chosen build, you need to burn the image to an SD card.  Generally balenaEtcher is recommended as it does a verification of the burn.  Also be sure to use high quality SD cards.
 
Once you have the SD card with your chosen build, then you need to edit the boot configuration file on the SD card.  In the BOOT partition of the SD card there will be a file /boot/extlinux/extlinux.conf, that you need to edit.  There will also be a extlinux.conf.template file to use as a reference.  You will need to add a line into the extlinux.conf file for the Device Tree (dtb) file you will be using for your box.  Place this line before the APPEND line as shown in the .template file.
 
Basically you need to have the correct dtb for your box.  You may need to attempt to use different dtb files until you find the one that works the best for your box's hardware (there are a bunch of dtb files in /boot/dtb/amlogic/... to try depending on your cpu architecture and hardware).  It is unlikely that there will be a matching dtb file for your TV box.  The idea is to find the one that works best for your box.  This may mean that you try booting with different dtb files until you fine one that works good enough for your needs.  By searching the forums you will find information about what dtbs other users have found work best for different boxes.  Because you are booting from an SD card, you can easily try different dtb files.  The dtd files are named by cpu family.  So for example dtb files for the s905x2 cpu are named meson-g12a-*.  Below there is a table that shows the identifiers for each familiy (g12a for s905x2 in this case).
 
Next you need to copy the correct uboot for your box.  This is needed for how these builds boot on amlogic boxes.  There are four different u-boot files located in the /boot directory:  u-boot-s905, u-boot-s905x-s912, u-boot-s905x2-s922, u-boot-s905x3
You need to copy (note copy not move) the u-boot file that matches your cpu to a new file named u-boot.ext in the /boot directory
So for example with a TX3 mini box that has an s905w cpu you would copy u-boot-s905x-s912 to u-boot.ext: cp u-boot-s905x-s912 u-boot.ext
(See table below for more details on which u-boot to use for which cpu)
 
Once you have your SD card prepared you need to enable multiboot on the box.  There are different ways documented to do this, but the most common is the "toothpick" method.  The "toothpick" method means to hold the reset button while applying power to the box.  The reset button is often hidden and located at the back of the audio/video jack connector.  By pressing that button with a toothpick or other such pointed device you can enable multiboot.  What you need to do is have the box unplugged, have your prepared sd card inserted, then press and hold the button while inserting the power connector.  Then after a bit of time you can release the button.  (I don't know exactly how long you need to hold the button after power is applied, but if it doesn't work the first time try again holding for longer or shorter times).
 
You should now be booting into armbian/linux.  Note that the first boot takes longer as it is enlarging the root filesystem to utilize the entire SD card.
 
After you are satisfied that your box is working correctly for your needs you can optionally copy the installation from the SD card to internal emmc storage (assuming your box has emmc). (Note: Installing to emmc has some risks of bricking your box.  Don't do this unless you feel you understand how to reinstall your box's android firmware)  You install armbian to emmc by running the shell script in the /root directory: install-aml.sh. Note: It is not possible to install into emmc on boxes with the s905 cpu (s905x, s905w, s905x2, etc however should all be supported).  It is recommended that you make a backup of emmc first.  Also be prepared if anything goes horribly wrong with your emmc install to reinstall the android firmware using the Amlogic USB Burning Tool to unbrick your device.  If you have or can find an original android firmware on the internet and you can generally (but not always) recover a bricked box using the Amlogic tool and the original firmware file.
 
 
Mapping from CPU to uboot and dtb:
 
u-boot-s905
s905 - gxbb
 
u-boot-s905x2-s912
S905X - gxl
S905W - gxl
S905D - gxl
S905L - gxl
S805X - gxl
S912 - gxm
A311D - gxm
 
u-boot-s905x2-s922
S905X2 - g12a
S922 - g12b
 
u-boot-s905x3
S905X3 - sm1
 
Not supported or not tested
S805 -
S905W2 -
S905X4 -
S805X2 - s4
A113D - axg
A113X - axg
 
 
 
Note: Followup posts in this thread should be limited to comments to improve or better understand these instructions.  Other issues should be posted as new questions in the Amlogic CPU Boxes sub-forum.

@balbes150 If I could ask a favor of you.  Would it be possible to add a tag to your public github repositories that corresponds to your last build supporting AML?  With a tagged version of source code that corresponds to your final released build others can pick up where you have left off if they are capable and motivated.  I appreciate your dedication to armbian and respect your decision to end your support of Amlogic cpus.

Technically Balbes never supported the s905x3. But it is true that he is now ending support of all amlogic cpus.  I already make my own kernel builds, and since I own a few different amlogic based boxes, I have an interest in seeing support continue in some form.  I have asked balbes in another thread if he would tag his public github repositories with a tag that corresponds to his last build supporting amlogic, which then can be a starting point for continued support by the community if there is enough interest.

moved topic to the proper forum

This comment is likely superceeded by balbes and jock's posts, but I wanted to just provide my thoughts on the android dtb issues. 
The way I like to think about dtbs is they are glue code between the kernel and the hardware.  We often think of them only from the perspective of the hardware, which once a box is built the hardware doesn't change (although boxes can change over the course of different manufacturing runs providing different board revisions).  But the kernel is an evolving code base and even though the hardware may be fixed, the dtb glue may need to change over time as the kernel code changes.  Thus technically dtbs are kernel version specific (but in practice the changes in the kernel generally are not significant over smaller periods of time).
However....  When it comes to android kernels two factors come into play, one is that android kernels tend to be highly forked/patched from mainline kernels and second, android kernels tend to be based off very old kernels.  So for example an android 4.4 based kernel is really a 5 year old kernel, and a lot has changed in the kernel over a 5 year period.
Also, making this more complex is that fact that sbc/tv box support has only been added to mainline kernels fairly recently.  So older android or legacy kernels that were supported were highly patched kernels.
Armbian is generally focused on current mainline kernels (after all that is where the future support will all take place), and therefore a 5.10/5.12 kernel is very different in how it supports sbc/tv box hardware than a 4.4/4.x legacy/android kernel. 
The end result is to not expect an android dtb to work with a mainline kernel.  That doesn't mean that there isn't a lot to be learned from an older dtb file, but the process is much more complicated than simply getting the old andoird dtb and using it on a mainline kernel and expecting it to work.

The first place to start is by reading the documentation:  Armbian Developer Guide.  The developer guide walks you through the armbian build process.  The entire armbian build process may be more than you are looking for (not knowing what changes you are looking to make), but with an overall understanding of the armbian build process (simply being able to rebuild the image you are already running) you will likely be able to figure out a path forward for your needs, or at least be able to come back to the forums with a more specific question based on greater understanding of the system.

H6 is newer an has a way better GPU on it, and also a higher clock. Between them, H6 wins 
 
And mine is a T95 Mini (TUREWELL). It didn't arrive yet. Soon I'll be able to give support to it 

Given the following comment posted in response to the new invalid message discussed above:
 
"Hi Werner, I didn't realise I'd posted this as a bug I'll post it elsewhere"
 
I took another look at the language in the big red warning message that is displayed for people posting new topics in the bug tracking forums.  While it would seem obvious to those of us on the inside what we are trying to communicate, to the novice user I think there is room to make it more clear.  To that end I have the following suggested wording changes:
 
Current text:
 
Wait!
To avoid common mistakes when opening issues use this form to make sure you have collected all necessary information and create your issue report at the correct place:
>> https://armbian.com/bugs <<
Issue reports that are not following these guidelines will be removed without further notice!
 
Suggested text:
 
Important Please Read Before Posting a New Topic (Bug Report)!
 
You are about to post a new topic in the Armbian Bug Tracker.  Armbian uses the sub-forums under "Bug tracker - supported boards and images only" as it's public facing bug reporting system. If you really intend to report a bug please fill out the following form to supply the necessary information for a valid bug report:
 
>> https://armbian.com/bugs <<
 
With limited resources the Armbian project is only able to spend time investigating bugs where all the requested information has been provided and for only the boards/images/software that are supported.  Your bug report will be considered invalid and receive no attention if you do not supply the requested information.
 
If you only have a question or are looking for help on something in general related to Armbian, you should be submitting your question in one of the "Community forums", such as "Common issues / peer to peer technical support" or "General chit chat", not in this bug reporting forum.

I don't see a problem with using the invalid label as it is invalid according to the directions the user has read (or not read).  What I think would improve this is giving the user more direction on what to do next.  I think some working changes in the post that closes the thread as invalid would be all that is necessary.  So instead of:
 
 
Your issue report is invalid for one or multiple reasons (non-exhaustive enumeration):
 
it has been stated at the wrong place
it lacks fundamental requested data
it could have been easily solved by a quick search and/or reading documentation
unsupported userspace/image/SBC
 
Since you refused to use the bug reporting form carefully and follow the information there as you have been asked for we have no intention to further investigate.
Please add missing information if applicable.
 
https://www.armbian.com/bugs
 
 
Something like:
 
Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs).  With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported.  Your report is invalid for one or more of the following reasons (non-exhaustive list):
 
- it is for an unsupported board or image
- it is for software that isn't supported (such as userspace modules installed on top of the core operating system)
- it has been logged in the wrong forum (for example requests for help that are not actual bug reports)
- it lacks requested data (armbianmonitor output)
- it could have been easily solved by a quick search and/or reading documentation
 
Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as "Common issues / peer to peer technical support" or "General chit chat")
 
 
I think this softens the tone and tries to help the user do the right thing.  Which they likely still won't 
 
 
 

Your question was already answered the first time you posted your question.
There is an entire thread dedicated to discussing how to install armbiian on an rk322x tv box: https://forum.armbian.com/topic/17979-help-can-i-install-armbian-on-tv-box-with-r329q-v30-board/?tab=comments#comment-123847
 
 
This is now the third the you are asking the same question. It you ask a fourth time, I will consider you as spamming the forum and proceed accordingly.
 
 

Your question was already answered the first time you posted your question.
There is an entire thread dedicated to discussing how to install armbiian on an rk322x tv box: https://forum.armbian.com/topic/17979-help-can-i-install-armbian-on-tv-box-with-r329q-v30-board/?tab=comments#comment-123847
 
 
This is now the third the you are asking the same question. It you ask a fourth time, I will consider you as spamming the forum and proceed accordingly.
 
 

@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.