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.
Hi, I installed on my old x8-h. Occasionally, you cannot turn it on again with the button after turning it off. I need to unplug the power supply and reconnect it. Everything else works great. Thank you very much.
when the player is on, the LED is off, but when it is off, the LED is on.
Unfortunately, I can't help with the LED because I don't have such a device and the DTB doesn't include an entry about the GPIO pin of the power LED either. 
But the power-on error is probably caused by an uboot bug. Please try the description in the first post to avoid this error.
You can find the relevant section here: Fix the "power-on bug" in uboot for some boxes (S8X2 only).
If the same error exists on the Minix bootloader, it will probably help.
Can someone please remind me the command that returns the dtb/bootloader version that the os uses for the tvbox?
It is cat /sys/something/something
What you are looking for is not accidentally the device-tree ID?
cat /proc/device-tree/amlogic-dt-idNB: dtech If you do find a Core for sale anywhere that takes PayPal we're happy to fund it.
I appreciate the help, suddenly I don’t even know what to say... Thank you. 
Just for info. In German eBay kleinanzeigen there are 3 wetek core on sale at the moment. Between 50 and 60€.
If you really want or need one, I can play proxy for you.
This may interest me, but how do we do this "proxy" thing?
You buy the box to your own address, I (or we) make an electronic money transfer to you and you send it to Hungary to my address?
maybe you can get a wetek core here:
This is actually a WeTek Play 1 device. Thank you, but I already have a WP1, and luckily it is flawless.
But I haven't found WeTek Core since.
Tested it and all 3D sound formats (DTS-X, Atmos, Auro 3D) work now.
Thank you very much for the quick solution and your effort
I wait a few days and if no further bugs come up, I will publish this image as a stable version (v9.2.8.2).
Thank you for the feedback. 
Thank you very much.
In principle, I manage to fix the audio passthrough issue:
The TrueHD/Atmos works now, but please give it a try too, because I cannot test DTS-HD on my TV.
(snapshot directory link removed) -> http://libreelec.dtech.hu/S905/
I used "AlexElec 3.3.1" which is running Kodi 18.9-Leia and Kernal 3.14.
However, yesterday I also noticed that when I put Kodi 19.1 on the Android system of my K1 Pro, the HD audio formats (Atmos/DTS-X) also work.
This version here is the first that I have problems with the playback of HD sound, although the settings are identical (passthrough enabled and checked for all sound formats).
Okay, I retracted my previous statement because it doesn't work for me either. I will investigate this error.
I even flashed back to my old system (the output of the HD sound like Atmos/DTS-X worked again) and then re-installed your image which again led to the fact that the HD sound formats no longer worked.
What does the "old system" really mean? (OS name, version and kernel version.)
Hello,
is it a known problem that the playback of HD audio (Dolby TrueHD/Atmos, DTS-HD/DTS-X) does not work? The passthrough for each format has been activated, but I hear only a creak on my K1 Pro.
Are you trying via HDMI or S/PDIF? Is the receiving device compatible with these formats?
Via HDMI the Dolby TrueHD/Atmos passthrough works for me without problems on my LG OLED TV, but I can't comment on DTS* because it doesn't support it.
I got my one here a few days ago: WeTek Core Mini Android Box Full HD 1080p 4K WIFI Quad-Core Mediacentre IPTV App | eBay
Is the new image able to run a browser? Chromium seems only to be working on x86
Unfortunately, that doesn’t help because mine also came from here and they don’t seem to have more pieces yet.
Although I contacted the distributor, I have not received a response so far. (I hope there is another one deep in the warehouse.)
Sorry, but I have no idea if the browser works, although I wouldn’t think of running a browser under Kodi.
I think browsers run better on Android than a media center OS. Hardware acceleration certainly doesn't work under LE on a browser.
