1. The G12 platform (s905x2 s922x a311d) now uses a single image (it also works on N2).
2. For the Odroid N2 model, I only check the option to run on USB media using SPIboot.
3. Addons are transferred to the new Kodi-19 platform, there may be failures and not correct operation. Therefore, it is recommended to test a clean install\run (without using the update via TAR).
Image update 20191019.
There is interesting information about co-running the same image on two platforms simultaneously rk3399 and rk3328. This will further allow to have a shared image for rk3399 and rk3328 when upgrading via TAR. The details there is in this topic.
https://forum.armbian.com/topic/8263-armbian-for-rk3399/?do=findcomment&comment=87869
It would be useful to test this option on different rk3399 and rk3328. By the way, the latest Libreelec and Armbian images use a common u-boot-2019.10, the difference is only in the configuration for the two platforms when building.
In the latest build Kodi 19 does not start (LibreELEC-RK3399.arm-9.80-devel-20191011115114-6e9040d-box.img) I think you forgot to link the libraries:
You took the version with kernel 5, this is a very new direction and a lot of things may not work from version to version. It is intended for General tests.
at the moment I don't know how to start the NanoPC-T4 from USB, so I haven't tested it yet.
See the posts in the topic. Verification is very simple. To write the image Armbian to SD card (do not need to configure DTB). The image on the SD card is only needed to run u-boot, then it should start from USB. Write to USB flash drive LE with kernel 4 (you can use any working version of LE). Configure on USB correctly DTB. Connect SD card and USB flash drive to T4. Turn on the power and wait 3-4 minutes. If nothing happens, you need to try to connect a USB flash drive to another connector USB. Start your tests with USB 2.0 connectors. I have on EDGE and on Magicsee N6 now in eMMC already installed the latest version of LE (20191011 with kernel 4) and now I can quickly run different test systems from a USB flash drive.
What is the difference between the images (desktop and normal) ?
Versions of Armbian called Desktop have an XFCE GUI. Default images are server images.
I tested your new image
The latest versions of Libreelec (and Armbian) added the to start the system from USB media. Can you test this new feature on your T4 ? Details can be found in this topic.
https://forum.armbian.com/topic/8263-armbian-for-rk3399/?do=findcomment&comment=87554
I was about to try the two u-boot bin files you asked me to download when I notice you had them removed. Sorry I was busy with other things so I haven't had the time to try.
Try the latest version image 20191008. Preferably with UART output.
Can you test this test image with kernel 5 on T4 ? On EDGE at me KODI does not start, I am interested that will be on T4 with that DTB which is a part of an image.
New image 20190928 with support for new binary Addons for KODI-19.
New image 20190927 KODI-19. Added several addons.
Display MoreHi balbes150 each time someone ask for migrating from CE or activation of multiboot, you point to this message.
Sorry, but really I cannot see any instruction for installing such multiboot.
Is there a document describing what is really required for installing multiboot?
In the post you have pointed there is written that a firmware restore is required. Assuming that can be hard for some box to get the OEM firmware, why should it be needed? CE actually changes nothing in the original bootloader, it is the "reboot update/toothpick" method that instruct uboot to look first for a bootable media instead go for eMMC
And what happens if someone what to switch between CE and LE back and forth?
Bye
what information do you need to create a dtb for an S905X2 box? I have here a Bqueel y5 with S905X2 4gb
I don't have that kind of equipment.
I had Coreelec installed
There seem to be old binaries in your image, because the version KODI 18 or higher should be included, right?
Add new image 20190925 KODI-18
You can certainly PM me.
If you are a corelec developer, you can get all the information from a representative yourself. I will send you in PM details of the official representative of the manufacturer. Further, you do communicate with him and ask your questions (to avoid accusations that you were given a lie).
let's keep it factual, please
Specifically for HK I have no official information, but I have official information about such requirements from corelec from another manufacturer. I can send you in PM the details of the official representative, what would you do he got this conversation. He didn't ask me to keep it a secret, but the exact details of the deal, I'm not authorized to divulge. 
That is so pathetic coming from a Moderator.
You might as well move the Forum Rules to the TRASH
1. you better feel sorry for yourself and the rest of your group (corelec) if you don't know what's going on behind your back. 
2. I do not care who exactly you have in corelec takes a bribe from manufacturers. For me important is only officially confirmed by the manufacturer, the existence of such bribes.
3. I would like to draw your attention to the difference between sponsorship of any project and a strict agreement on fixed contributions. The sponsor himself determines the size of the voluntary donation, and he decides whether to do it or not (no one forces him to do it). If you take a bribe, it is already a commercial project, which is aimed at obtaining maximum benefits. 
I am privy to all CE matters being part of the team and say you are BOTH wrong in the quotes you have made.
Are you sure you are privy to all the questions of charging bribes from producers (This is not just about HK) ?
It's funny, the Ce team doesn't know what's going on behind their backs.
Balbes, In kodi 19 waipu tv is integrated as a pvr client. But not in your image. Of course, I don't know what's available to you. Thank you for your great work.
There are no binary Addons for KODI-19 yet. Use versions with KOD-18
store init 3
This command full erases all eMMC.
First, try in the UART console to run the command "defenv" and then the second command "saveenv". This will reset all variables to their original state. After that, you can try to write the regular firmware via USB Burn Tool.
After that, you can normally activate the multi-boot and run the LE from external media and install in eMMC without the risk of killing the TV box.
