Another approach:
I made two kernel images with the right dtb, please follow my description.
First, use this image again for prepare the SD card:
LibreELEC-MXIII-1G.arm-9.2.7.img.gz
Then download this, extract and overwrite the files on the card with these (kernel.img, kernel.img.md5, dtb.img):
LibreELEC-M8.arm-9.2.7-kernel.img+dtb.tar.gz
Then boot your box from this SD card and test the Ethernet.
If Ethernet still doesn't work, try this:
Can you add S89 cable network card IC + ip101gr 10 / 100 Ethernet driver to n200-ap6330_ 2G inside the support, to achieve S89 start normal, Ethernet normal
It is already supported: LibreELEC-AML/linux.arm.conf at a292f0ec2ac492266937dadd349d90e47106e772 · dtechsrv/LibreELEC-AML · GitHub
I have realized in a circle that replacing the DTB does not solve anything because the 3.10 kernel does not deal with external DTBs. 
I'm trying to find another solution...
Hi again, thanks for your suggestion! I tried 9.2.6 but the same thing happens... Installation -> Reboot -> splash screen -> black (but with mouse cursor)
Unfortunately, no one from the X8-H Plus image has ever indicated that it works.
TheBronx tested my M8S+ image on an X8-H Plus (#50), but by the time I was done with the X8-H Plus image, unfortunately, he had given up, so I never knew if it would work or not. It seems to be not working at all.
The only feedback I got was from a plain X8H from Blackomega35, which works even if it only has an S802 SoC in it.
Please try my M8S+ image on an SD card, because that image uses a modified initramfs.
The remote control, wifi and a few little things (like temperature) won’t work, but if it boot, we're already ahead.
But DTB, I can't understand, so I can't solve it by myself. I hope you can help me adapt it!
Okay, I found something that will hopefully be useful.
The Tronsmart Vega S89 device (it doesn't matter if it's Elite or Standard) is based on a Meson8 reference board type "k200" layout.
First, use this image to create the SD card:
LibreELEC-MXIII-1G.arm-9.2.7.img.gz
I found two devices with the same type, you should try this first:
The downloaded file must be renamed to "dtb.img" and the existing one must be overwritten on the SD card.
Then try booting from SD card and check Ethernet connection.
If Ethernet still doesn't work with the first dtb file, you need to try this one:
Logs here: log-2021-06-13-09.25.38.zip
Have you tried the v9.2.6 image yet? Please give it a try because I have a suspicion that the v9.2.7 image for the X8H-Plus is corrupted.
You can find the older image in the archive directory: Index of /3rdParty/S8X2/X8-H_Plus-S812_2G-AP6335e/ARCHIVE/. (Link fixed.)
Hello,
Does the Beelink MINI MXIII II 2 GB/16 GB work for the LE-9.2.7 build from s905x devices? Thanks!
Your device should work with the "MXQ-4K-Pro_2G" image without any modifications: Index of /S905/.
But DTB, I can't understand, so I can't solve it by myself. I hope you can help me adapt it!
I will compare the two DTBs because the Tronsmart S89 also uses IC+ IP101GR 10/100 Ethernet transceiver and the kernel already supports it.
Good afternoon, if there is an opportunity, tell me where you can find the latest LIBREELEC firmware for Mini M8S pro, some time ago I was able to install the old version, now I can not find anything.
I'm sorry, but I don't have any S912 device, so I can't afford to support it yet.
Can it be the problem of NTP? The time NTP we use in China is ntp1.ailiyun.com
My model is the same as the tronsmart Vega S89
No, NTP certainly does not cause the error. I would need the original dtb from Android.
This time, it seems to connect to my network, since my router picks it up and gives it an IP. However, when SSHing to the box, I get "Connection Refused".
Unfortunately, SSH will not work before setting up the installation wizard. Try accessing the "Logfiles" share via Samba instead.
I started a conversation between us, please read it, because I'm waiting for your test. (Conversations)
Thank you. 
Then restart, unable to enter Kodi
Are you absolutely sure that you have an S802 SoC in your device and not an S812?
Please try this one: Index of /3rdParty/S8X2/Universal-n200-S812_2G-AP6330/
This is a universal build for multiple n200-based S812 devices with 2GB of RAM.
I am a player from China, my English is not good, basically rely on translation!
I have a Chinese made Yingchi gal-x2159 AML S802 with 2 + 8 100m network card, 2.4G + 5.8G + Bluetooth 4.0
Your libreelec-m8s-plus.arm-9.2.7.img.gz on SD brush can be fully activated,
But the wired network cannot be used, and the IP obtained is 169.254.xxx.xxx
Can I add support in the next version!, thank you very much indeed
For the S802 SoC, the KII dtb is definitely not good.
You need to try this image first:
MXIII (S802, 1GB RAM, 10/100 Mbps LAN, AP6330 WiFi):
Index of /3rdParty/S8X2/MXIII-S802_1G-AP6330/
Hope that gives you some more clues, dtech.
Well, I'm more clueless right now than I used to be. 
Let me know if you need anything else from me, dtech!
Okay, this is really an AP6210, interesting. 
Could you also send a dmesg from my 9.2.6 build? I wonder where it gets stuck.
Can I use that too on my mxqpro 4k (device tree gxb_p200_1g)?
Omg, I feel like Obelix asking for a sip of the magic potion
Dear Obelix,
You can use it, but the signal strength of your wifi won't get better. 
However, if we are already here... With kszaq's 8.2.3, what was the signal strength of your wifi? Better or similarly bad?
The question also applies to the S905 and S805, of course only if you have tested with this version before. If not, consider it irrelevant.
The new 9.2.7 image is ready for the test: LibreELEC-MXQ-4K-Pro_2G.arm-9.2.7.img.gz
Please use the previously linked dtb and remote.conf for this image.
Thanks for the new MXQ-S805 build, dtech!
Unfortunately, bluetooth still doesn't work with this build on the MK808B+. Any other ideas?
Okay, I need a dmesg under 8.2.3 because now I'm not sure you have an AP6210 in your device.
And then, one more thing ...
cat /sys/class/net/wlan0/device/vendor
cat /sys/class/net/wlan0/device/deviceThis is really true now the remote is working, thank you dtech
Will you make a device tree for RTL8723BS wi-fi ?
The reason for the non-working wifi is not the dtb, because this driver is basically missing from the image.
I will include it in the next release (9.2.7), but it’s a good question when I can make it, because I should solve the Widewine issue before I release it for S905.
Edit: restore previously removed wifi drivers and firmwares · dtechsrv/LibreELEC-AML@aeb4c61 · GitHub
RTL8723BS Wireless LAN 802.11n Network AdapterWe are moving forward.
Oh ok. I am staying at the previous image because my mxq is indeed all black.
I will try to update the Realtek WiFi drivers later, but now unfortunately I am struggling with the Widevine CDM issue.
I successfully migrated version 9.2.7 (officially released exclusively for RPi devices) to 32-bit only S8X2 devices, but for some reason it doesn't really want to work on the 64-bit S905 branch. 
I already have a working (and configured) installation of le 9.2.6 on my (s805) mxq from your images here.
Is it worth doing a fresh install from the images you made today? I assume I can back up my current configuration and restore it when the new image is installed. I am interested to see if it solves the the wifi connection issues I have (message 74).
This image is not made for the MXQ "all black" boxes (HD18Q/m201d), it is for the MXQ-S85 (which has a red "MX" stripe and a button on the top) and the MK808B+ only.
Otherwise, this image only affects Broadcom wifi/bluetooth drivers, so unfortunately this may not solve the signal strength issues with Realtek chips.
Thanks for looking into this, dtech!
If you need a hint, kszaq's MXQ 8.2.3.1 build has bluetooth working for the MK808B+. See RE: [8.2.3.1] LibreELEC 8.0 for S805
I made a new image that already has the correct remote control config.
I restored the original wifi/bluetooth stack so this version should be checked to see if it works:
Index of /3rdParty/S805-LE-9.2.6/MXQ-S85/
Hi dtech - the dmesg log - Untitled in plain_text (s35bms77qe) - PasteCode.io
Please notice and remote control, because I have problem with remote too, I try to make own remote.conf but when I press a key nothing is logged with "dmesg –c"
Unfortunately, dmesg doesn’t tell us anything about the wlan interface.
Please try this under LE 8.2.3:
lshw -C network... and this:
cat /sys/class/net/wlan0/device/vendor
cat /sys/class/net/wlan0/device/deviceHowever, dmesg revealed the configuration of your remote control.
You need this: remote.conf