What image to choose for odroid N2 and also possible install to emmc card?
The amlg12 image runs on N2. In the LE settings menu, there is an item to create a full eMMC backup before installation and an item to install LE in eMMC. For quick and easy testing of systems from different media (including USB flash drives), I recommend switching to SPIboot. The details there is in this topic previously.
EMBY
I'm sorry, I didn't understand what that means, what needs to be checked ?
The new version 20191123.
with updated some Addons.
New versions 20191123 with update Addons.
Added on site version of way of 20191120 with core 5 on base Panfrost. There is no HW decoder yet, but the performance of rk3399 is quite enough for SW video decoding with 1440p (1080p screen resolution). Tried with USB stick on the N6, all of the test videos worked. 
Did you find a box? Looking for something with similar specs, only be using it to play mkvs from external hard drive. Could do with gigabit LAN as I have 1000mbps internet. I've done a lot of reading on this thread but feeling a bit confused... I suppose the simple solution would be a Minix U9 but that's almost Nvidia Shield money where I live!
Currently using a cheapo x96 s905x 1gb ram box that I had gathering dust in a drawer, it works but sometimes buffers or freezes with high bitrate 4k mkv's.
To date, a reasonable option for the ratio of costs\the result is Ugoos x2pro 4\32 or cube 2\16 (2 GB of RAM is enough to play media content). This model has full support for all elements (including WiFi) on core 5. If you don't need built-in WIFI and need maximum performance, you can use the AM6 (with metal body and excellent passive cooling system). These models use the best Android firmware (with long-term support for updates), with support for universal multi-boot. This means that you can immediately and easily run any modern system (LE, Armbian, Manjaro etc.) from external media (including USB 3.0 with a speed faster than eMMC and no volume limit of up to several terabytes) and fully retains the ability to automatically update the standard firmware via OTA.
Just for interest I looked into android_enable/disable scripts..shouldn't the correct echo-line be: echo "Start disable reboot from Android" in the DISABLE script like I altered in mine on the picture
This is the service information that remained after debugging and it does not affect anything.
connect the USB to a free USB3 port.
Then the NanoPC-T4 will boot normally.
This version already has support for starting from USB. You can easily run test systems from any conventional USB stick. It's much easier than using an SD card.
Write the image to a USB stick, configure as usual DTB, connect the USB stick to T4 in USB port and turn on the power. After a few minutes, the system should start from a USB flash drive. If nothing starts after 5 minutes, you need to find a port from which the system can start. You need to try to connect the flash drive to other ports and check the start.
All versions (with kernel 4 and 5) run from USB media. The latest version 20191117 with kernel 5 I run on N6 (Kodi-19 interface works), but the video does not work yet.It is interesting to check the running of kernel 5 on T4. It would be good if there were users with NanoPI M4 and checked the launch of LE on this model.
work flawlessly with me.
If it's not a secret, what version of the LE image (full name) do you have installed in eMMC ?
Installation in eMMC works well for all rk33xx TV boxes. To do this, the system has special menu items in the settings (menu eMMC). I pay attention, before installation in eMMC it is necessary to make a full backup of eMMC (for this purpose there are also special items in the menu). The process of creating a copy can take up to 20-30 minutes (depending on the speed of the eMMC and the media from which the LE starts). After the backup and installation is complete, the system itself shuts down.
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
