Maker39

Since the changes from 10.04.2020 and the replacement of images on rk322x-box.
Firmware replaced with new ones.
LE_bootloader_Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal 2GB
LE_bootloader_Armbian_20.05.0-trunk_Rk322x-box_buster_legacy_4.4.194_minimal 2GB
LE_bootloader_Armbian_20.05.0-trunk_Rk322x-box_focal_legacy_4.4.194_desktop 4GB
These are img from first post with Libreelec bootloader for boot without erase eMMC. Just insert a card and turn on power.
 
Google Drive https://drive.google.com/open?id=1uoQvZUUFZyCWYFtatlTSJvJSSjUuJYLm
 
26.06.2020
Because at the moment, the firmware has lost its relevance. Deleted.

All the images in the first page have been updated with the following news:
Single image for all boxes! Configure your box with sudo rk322x-config once the system has booted Support for Realtek 8188eu, 8189es/etv, 88x2bu and various other wifi chips General better stability eMMC in DDR mode for some boards Enjoy!

Тhanks it worked.
 

@Maker39

try
it should pull only the 3229 branch

and then go to expert mode and tvboxes sub menu

EDIT: regarding 8723 try to load ONLY the 8723cs   be aware of cs

and blacklist all other 8723.

study still going on because at every reboot it changes mac address

@Alessandro - you may try the following on a linux system, assuming your sdcard is in /dev/mysdcard (whichever device this might be in your case):
"zcat working Librelec-xyz.img.gz | dd of=/dev/mysdcard bs=512 count=32768 status=progress"
then use "fdisk /dev/mysdcard" to create a partition starting at sector 32768 (something like o, n, p, 1, 32768, enter, w, q - might be wrong - all off mind) and then dump the armbian image to it:
"xzcat Armbian-xyz.img.xz | dd of=/dev/mysdcard bs=512 skip=8192 seek=32768 status=progress"
and then try to boot that sd card - i think the armbian image uses an offset of 8192 sectors (@jock please correct me if i'm wrong here) - i never tried it this way, but in theory it should work and maybe be the fastest way to get libreelec boot and armbian rootfs combined
 
good luck and best wishes - hexdump

@Maker39
 
I compiled a new "experimental" mx4vr image with 8189es driver, which supports also 8189etv, you can find it here
Also you may get just the 8189es.ko module object from here and try to modprobe it.
 
You may also try to modprobe 8723bs driver to see if 8703bs chipset is somehow supported, I saw some crossreferences in the code but no specific driver anywhere.

I can summarize the subtotal.
My board T95N-RK3229_512X4-20170803_V1.5  (include SOC RK3229, RAM K4B2G0446D, Wi-fi SV6051P,  this TV-Box Iconbit XDS8) works with the image Armbian_20.05.0-trunk_Xt-mx4vr-v01_focal_legacy_4.4.194_desktop.img
But need:
1. unblock SSV6051 in /etc/modprobe.d/blacklist-xt-mx4vr-v01.conf
2. manually set date-time , and/or install ntp client for correct update packages
3. surely something else...............
 
Thanks @jock for the work and advice 

I can summarize the subtotal.
My board T95N-RK3229_512X4-20170803_V1.5  (include SOC RK3229, RAM K4B2G0446D, Wi-fi SV6051P,  this TV-Box Iconbit XDS8) works with the image Armbian_20.05.0-trunk_Xt-mx4vr-v01_focal_legacy_4.4.194_desktop.img
But need:
1. unblock SSV6051 in /etc/modprobe.d/blacklist-xt-mx4vr-v01.conf
2. manually set date-time , and/or install ntp client for correct update packages
3. surely something else...............
 
Thanks @jock for the work and advice 

@jock

was my mistake, i suggested maker to use r329 q but i missed that is a mmc
 
@Maker39
 
sorry for that follow jock suggestion
 
about wifi yes it makes two connection , a p2p and a managed one

to choose the right one you can try from ssh with command
 
nmtui

and then activate a connection

@Maker39 which image did you use?
Don't use r329q image: eMMC on that image is deactivated because r329q boards have NAND chips instead of eMMCs.
 
You should use xt-mx4vr-v01 images instead: you posted a dmesg log from the xt-mx4vr-v01 image that shows the emmc is detected and should work fine. Be sure that  lsblk utility shows mmcblk2 device

@Maker39
Download a new fresh copy of the legacy kernel image.
 
You were just unlucky because for a bunch of days during early march I uploaded an image which was not working: initramfs compression changed to lz4 and I forgot to enable the kernel flag.
 
The mainline kernel is still a bit itchy, especially if you have an RK3228a device: despite most of the boards are sold as RK3299, they may actually have rk3228a, rk3228b or rk3229 socs.