My guess is that you have a clone device and it is a gxbb (s905) platform, that would explain the PLL error. I'll send you gxbb blobs, well worth a try…
I don’t want to have a say, but you could try it with the image I made in the same way. (Extract the content with the customization tool.)
I only dare to suggest this because the same model of device has already been revived with it.
LibreELEC v9.2.8.2 (2021-09-12) has been released for S8X2 devices only.
Changes since v9.2.8.1 (2021-08-14):
Images can only be published after testing and positive confirmation!
So far, this has happened to these devices:
Not-affected S8X2 devices: WeTek Core.
Affected but not yet confirmed (waiting for feedback):
If you would like to help with testing, please indicate what device you have and what you experienced during the test.
Only these images can be used for testing: (snapshot directory link removed)
After positive confirmation, the images will be transferred to their own download directory.
I do not wait anymore... (2021-10-11)
IMPORTANT!
If you installed it as an update and you have a problem installing addons, you will need to manually update the LE repository addon:
Bad news, I mainly use Nextpvr, pihole or adguard a bit of a shame it won't be supported, but it's good that at least you have refresh the old boxes
I would be happy to re-implement the support if someone submits it in PR.
Unfortunately, I don't have time to investigate lately. Since I don't use the docker, I couldn't even test it.
I only have a problem with the docker
"Cannot connect to the Docker daemon at unix: ///var/run/docker.sock. Is the docker daemon running?"
I have no idea what is missing.
From branch 9.2, along with the end of official amlogic support, aml-specific patches for docker support was also dropped.
The docker compatibility was not a priority in my builds, so I wasn’t really concerned with re-implementing background support.
The other thing is volume bar - it's missing with every skin - how to fix it?
I can't comment on that, I've never encountered such a bug so far.
No problem i can check it anytime.
There is a new snapshot image exclusively for "Universal-n200-S812_2G-AP6330" devices: Index of /snapshots/20210910/
Install to nand(no problems while installing) boots for ages so will use SD card as before.
I forgot that some clones are soldered with pretty slow NAND at the factory. 
I know it is just a quick fix and not a proper solution but better then nothing.
Let's give it a try: I'm going to replace the platform_init script with the fixed version on the MXIII-S8X2 branch as well.
When the new snapshot image has been compiled, I will send you a link.
the one with working wifi
Well, I would be wondering which image was the working one. Can you send a link?
The same solution... But this is not really a solution, it is rather just a bypass.
I think bootloader at this moment is this one OpenELEC-Amlogic.MX3G-L106.arm-bootloader(but don't have any idea how to check it) used to gain dual boot and boot from nand in kodi.
That does not sound very good. You would need the original bootloader for the device.
I don't know what was changed in it, but that may be the main reason for the SDIO wifi chip recognition error.
I think firmware was taken from Tronsmart - MXIII Plus_108L1_SD_160604 as box is just another clone(i think they didn't make any newer firmware for it) - i still have first FW for it so might try to flash it tomorrow unless there is another way to fix it?
The problem is that there are plenty of clones out of these. To determine the exact type, you need to disassemble the box and search for the factory firmware based on the PCB ID. But, if you are absolutely sure you have the factory ROM, you should restore it.
Until you restore the original boot loader on the device, unfortunately I can't help you.
In my LE versions, no modification is required for dual boot if the installation is done using the toothpick method.
After installation the aml_autoscript ensures that the boot from the SD card is always active when it is plugged into in the box.
But if all goes well, you can also install LE into the internal NAND with the installtointernal script that replaces Android, so you don't need an external SD card anymore.
I would ask if I can still count on your test or forget it all? Because I've been waiting a couple of days and you haven't answered yet.
It would be important because if you don’t want to help me anymore, I need to look for another user with an X8-H Plus.
looks like it's CHIPSET='Broadcom 4330'
SD\VID_02D0&PID_4330 == Ampak AP6330
Something is broken in your device, because you are the first MXIII user who indicate the freeze problem.
Didn't you accidentally crossflash with a wrong Android firmware earlier which is not fully compatible with your device?
The M8S+ wireless stack was modified in v9.2.7. It means the dhd module loads statically instead of the wifi_dummy service.
So, your module load failure with M8S+ image may be occoured by the dhd module.
The only reason is your current bootloader (uboot) cannot handle your integrated AP6330 correctly, because probably it is not the original one.
One last question: if I ever need to set a specific address to MAC, do you know the path/conf file that I can edit?
I have used this solution earlier on a few devices, and it’s worked out perfectly there:
SUBSYSTEM=="net", KERNEL=="eth0", RUN+="/sbin/ip link set dev %k address AA:BB:CC:DD:EE:FF"Of course, AA:BB:CC:DD:EE:FF should be replaced with the MAC address you want. 
Thanks again dtech, I´ ll do a new test ASAP.
BTW does this kind of change requires an entire new instalation using the GZ file, or can I use the TAR one just for updating the changes?
You can update with TAR without any problem.
I will be making a new image soon, which will include the ethmactool package. Maybe that will solve this problem.
Okay, it is done: Index of /snapshots/20210908/
If you can, please check if the situation has changed with MAC address detection. Thank you.
There´ s no freezing anymore. Now I can stop or change between movies, tv shows, among others during playback smoothly, without problem!
I am glad that this error has been solved. I also experimented a lot with that M8S+ before I managed to fix it.
Besides the MAC address thing, it´ s working as expected to a old box as this one... hope it helps anyone with a Minix X8/X8H Plus.
I will be making a new image soon, which will include the ethmactool package. Maybe that will solve this problem.
Please test with this new image and send a feedback on whether it works or not:
I would appreciate it if you could test your device with this rebuilt image as well.
Hi! I also have a KII Pro mecool with Soc 905D and 3.14 kernel. What device tree have you used? and did you get tvheadend to work?
Try this one for S905D SoC-based KII Pro: gxl_p231_2g_dvb.dtb
Tvheadend needs to work because the KI Pro has the same tuner. I recommend the "dvb-latest" module package for the tuner.
I try this one "20210903"
Please also try 20210901. It contain datrh's original startup scripts and original platform_init script as well.
Rebuild: Index of /snapshots/20210906/
I apologize. Please tell me, do you have any ideas for rtl8723?
Thank you
Unfortunately, I have no idea at the moment.
Previously, there was a box with exactly same integrated SDIO wifi, but it was an S905 box and it eventually started with the external module.
