Thanks for your answer. And another question I have to do. After installing the 9.2.8.3 in my tv box when i reboot the box the libreelec logo at the beginning had disappear. Instead of the libreelec logo I see a very long incomprehensible list of a text for a while and after that the tv box is booting to Kodi. Is there anyway to fix it ?
Okay, this is a new issue... Can I get a photo of that?
I'm not sure where it pulls it Kernel sources from...
LiserTV uses the HardKernel's own kernel-branch with a few extra patches:
Any OS can read FAT, and it will usually contain only a few files, written rarely - so efficiency etc. is not really an issue.
It is a little interesting that x86 has been forcing UEFI and secure boot (nightmares) for a long time, but for u-boot we still use a file system to load all boot files that doesn't even handle basic permissions. Okay, that's easy to store boot files on FAT... But is it secure at all?! 
Since Matrix (Kodi v19) the legacy amlcodec is no longer supported. The old kernel (3.10) is already very outdated anyway, so the only solution is to switch to the mainline kernel. At the moment the state of the vdec is pretty much WiP. However, there is some progress in this area (Meson 8* Lives!), but it seems that Kodi v20 may be the first to run on Meson8* devices.
There is a little TvH 4.3 backport for my legacy Amlogic LE-9.2 images: http://libreelec.dtech.hu/3rdParty/packa…E9.2_v4.3-1903/
Source repository branch: https://github.com/dtechsrv/LibreELEC-AML/tree/tvheadend43
Update:
I’m really trying to adapt it, but I'd rather just say experimentation. Now I have a working image, but I wouldn't say it's 100% done.
http://libreelec.dtech.hu/snapshots/20211122/ (Source: https://github.com/dtechsrv/LibreELEC-AML/tree/odroid-c1)
It contains almost all Kodi patches I have used for the boxes, including the fix for the IPTV problem, and I also enabled the dvb-latest driver package. However, the kernel of wrxtasy I used for this build is unfortunately very outdated.
Although I only have this board for 2 weeks. Before that, I only had boxes. 
For me, the u-boot is a whole new area, so unfortunately I can't answer your previous questions on the merits either, but all the experience comes in handy. If I understand correctly, you want a native ext2/ext4 partition instead of a squashfs + overlayfs for the system patrition, right?
Two Questions, is this MXQ-4K-Pro_2G.arm-9.2.8.3.img.gz will work in my box ?, as it says 2G ram where as my box is 1GB Ram, and another do i have to download this gxbb_p200_1G_mxq_pro_4k.dtb, and rename it to .dtb.? Can i extract & use the the .dtb file which is already there in my (LibreELEC-Amlogic.aarch64-MXSPlus-8.0.3-update) given by the supplier of the box.
Now I see you are trying to update with an S805 (m8b) image, even though you have an S905 (gxbb) device. This is not going to be good.
If you update your S905 with the HD18Q image, it is guaranteed to never boot again after you restart your device.
And chewitt is also right, because in Leia versions (9.0/9.2) for Amlogic S905x the kernel is 64-bit, but Kodi is only 32-bit.
I think you need to look for another sd card and create a clean install with this image: LibreELEC-MXQ-4K-Pro_2G.arm-9.2.8.3.img.gz.
This is the correct dtb for your device: gxbb_p200_1G_mxq_pro_4k.dtb, it should be renamed to dtb.img and overwrite the original.
Everything looks good from the kernel side, I think the boot logo has been replaced by a custom ROM. If you can tolerate to see the OE logo appear on startup, you don’t have to deal with it because it doesn’t affect anything. However, if this bothers you, you will need to restore the factory Android ROM (this will restore the boot logo) and then install the LibreELEC image from the SD card to the NAND (with installtointernal script).
And to make CEC work, the fw_setenv cecconfig cec1f I wrote earlier must be run, because fw_printenv says it's still turned off:
cecconfig=cec0Thanks i copied .tar to .update folder, but it says this image is Uncompatible with my Hardware. I guess i have to use the previous version, can you recommend which is the last working version according to my specs.
The reason for the incompatibility is that the device name is different.
You need to create an empty .nocompat file next to .tar in the update directory, and try again. 
All you need is the correct dtb.img (gxbb_p200_1G_mxq_pro_4k), it will need to be replaced in the new version. But if you install it as an update (*.tar), you don’t have to do that either. However, I don't really recommend updating from 8.0 to 9.2, before that do a backup under Kodi.
dtech no sd card, I must have had openelec on there before I installed libreelec and I think it's getting the openeelec logo in something like 'bootloader config' before kodi even loads?
where do I find the uboot settings?
cheers
Can I get a dmesg and an fw_printenv output?
it still has an openelec splash screen on boot, any idea how to get rid of that?
Well, that's very interesting, because the LibreELEC logo is part of the initramfs, which is in the kernel.img.
If you are running LE from an sd card, please enter this command under SSH:
md5sum /flash/kernel.imgIf you do not get this result: ec3c1d0e0774093d2eabf6deb599f28f, the update failed for some reason.
(But if you are running LE from NAND, this command will not work, because there is no kernel.img under the "flash" mount point.)
and even though it says CEC connected on startup it doesn't recognise my Samsung remote?
Try to enable CEC manually in uboot:
fw_setenv cecconfig cec1fThen restart the box...
My HD18Q image from the LE 9.2 branch can be used on the MK808B+, but unfortunately bluetooth won't work.
If this doesn't bother you, you can find the image here: http://libreelec.dtech.hu/S805/
Related topic:
Hi, dtech
LE10 for Amlogic S8xx or s9xx?
Hopefully both. But this will probably be a longer story...
LibreELEC v9.2.8.3 (2021-11-05) has been released for S805, S8X2 and S905x devices.
Changes since v9.2.8.2 (2021-09-12):
For download links, please check the first post in this topic: #1
Mirror (GitHub): Release LibreELEC v9.2.8.3 for AML S805/S8X2/S905 (2021-11-05) · dtechsrv/LibreELEC-AML
Notice: The S8X2 group also includes WeTek Core.
I would like to say a huge thank you to the LE team, especially chewitt and also tavoc for their contribution in getting another one instead of my faulty WeTek Core device. This is probably the last LE 9.2 image I have published, from now on I want to help build and test official versions (LE10+) based on the mainline kernel for Amlogic devices.
The solution to this problem can be found here:
hi there. I have a S905 box using the DTBs from http://kszaq.libreelec.tv/s905/8.2/device_trees/S905/ - specifically gxbb_p200_2G_1Gbit_OTG_Port.dtb . Can you please add support for loadable DTBs?
When booting from external storage (sd card or usb flash drive), the DTB replacement works.
I recommend the IMPORTANT NOTES - Please read them carefully before asking section of the first post on this topic.
- Using an external DTB only works with the S905/S905X/S905D, but also only when booting from the SD card or USB storage.
If you want to boot from external storage with an external DTB, you can find it here: Index of /device_trees/.
But... Booting from internal storage will never work on my builds (except for listed devices), because the list of Android partitions may be different for each device, and if you don't know where /dev/dtb is, it's pretty hard to load it. The partition list for some devices is specifically defined in the DTB, so which came first: the chicken or the egg? 
(You need the DTB to know where the DTB is located. Nice paradox...)
And since I’m not making universal images for S905x devices (like CE), please don’t expect that from me either.
The only "relatively fast" solution to the internal boot is to replace the DTB integrated in kernel.img with mkbootimg_tools.
The slower but better solution is to build your own build for your device based on my source code.
Things should be concretized a bit...
What exactly device do you have? The title of topic is M9Splus, you are writing M8Splus below.
Also, it doesn't irrelevant if it's an OTT M8S+ (S812) or a Mecool M8S Plus DVB (S905*).
For the second device, I’m not surprised that WiFi doesn’t work because there is no open source driver for the SCI 9082C chip, so it won’t work with anything other than the factory Android.
Furthermore, which version of LibreELEC did you try?
Edit: Even in addition to the above, there are a couple of types of products called M8S-Plus, so it doesn't irrelevant how the name is written. A photo of the box (especially the insides) might be simpler.
