The reason for this is the following:
AMLOGIC
...
To set expectations, here’s the ‘No’ list:
- No support for updates from older LE releases (clean install is mandatory)
- No support for internal eMMC install except WeTek Hub/Play2 and SBC boards
- No support for SSV6501 and S908CS WiFi chips
- No drivers for in-box DVB tuners
- No hardware deinterlacing
- No HDR to SDR tonemapping
- No formal support for newer S905X2/D2/Y2, S905X3, S922X, A311D devices (read below)
Only managed to boot from MXIII-1GB image, but then the "read only" known issue
Please try the n200 image with this kernel:
Index of /_TEST_/MXIII-G_1GB-kernel/
If it starts with this, your Android is unfortunately only lying that you have 2GB of RAM, but in fact it only manages 1GB.
The root of the problem doesn't start here, as I see. I think your box does not have the original ROM with the factory bootloader, because based on the photos, there are 4 pieces of 512MB Samsung K4B4G0846C chips on the PCB.
So, in short...
Your box is equipped with 2GB of RAM, but it seems that the factory ROM has been overwritten. You should first find the factory ROM for his box from somewhere and flash it. If you're done with that, you should try the Universal k200 image. (But this wifi chip really won't work.)
Hi all,
Is't wifi WPA3 supported?
I'm not able connect to wifi with wpa3 from my minix X8H-Plus.
The box is older than the WPA3 protocol itself. Do you think its wifi chip supports it?
Please don't be so naive, handling encryption requires hardware support physically integrated into the wireless chip.
As far as I know, time travel hasn't been invented yet... 
I use the air mouse, the remote.conf contain this ?
No, it's a standard USB HID device, you don't need anything, it will work.
Can I run from sd-card the Legacy version of this?
Absolutely. You need to use Generic_S905 image and gxbb_p200_2G_minix_neo_u1.dtb.
And, if you use it with the factory remote control, you should save remote.conf from your old system.
After burning bootable SD card with Legacy v9.2 img there is no uEnv.ini to edit and "dtb" folder with device-trees...
There is "dtb.img" file which have to be replaced by correct file from "device_trees" folder - i did that many times with several files...
No success...
I would only know why I wrote a description in the #1 post, if nobody ever reads it. It is almost 100% that the toothpick method was not performed.
Another detail. The option to open the game with PS emulators does not appear. Both are already installed. I know that I must also provide the BIOS. That if it works.
Unfortunately, game stuff is outside of my area of interest, so I didn't delve into it at all. Originally, my repo didn't include it, but since several people requested it, the binaries that contaided in LE 9.2 were included.
Unfortunately, all I can still say is that if anyone encounters any bugs and has a solution, I'd be happy to PR them on GitHub.
Great job, tried few images on S805 and S905L everything is perfect, many thanks to Dtech.
One of my TV boxes is with Amlogic Meson8b (S805) SoC and the image LibreELEC-HD18Q.arm-9.2.8.7.img working geat in eMMC, but there is no Docker and no way to install it. As i need Docker most than anything else, how this can be done?
Unfortunately, there is nothing you can do to make it work. Under the 3.10 kernel, Docker simply cannot work.
Quote from the "IMPORTANT NOTES - Please read them carefully before asking" section of the #1 post:
- Docker only works under 64-bit SoCs (S905/S905X/S905D), it is not available on 32-bit systems (S802/S805/S812)!
I tested and saw that extFAT does not work 😞. NTFS doesn't even hold out hope for an older kernel.
Well, the fact is that both file systems supported: exFAT and NTFS. Most likely, your box is not able to supply enough current for the HDD, so it won't start at all. But since the factory DC adapter of these boxes is usually 5V/2A, there is nothing strange about this.
Accidentally, I discovered that I can put the system even one SD and a second stake in an external HD (keeping the name and format ext4).
A survey: put backup and format a second partition in FAT32 or extFAT?
It is not really clear to me what and why you want to format. Do not do anything with the data medium on which LibreELEC is installed, because its partition layout is fixed. If you modify a partition on it, LibreELEC will no longer boot properly. However, with other media you actually do what you want.
Before that, coreelec 9.2.x was installed. I got the 2 tvboxes (mxq "all black" and mxqpro4k) the same day, but because you only provide images for the one with s805, I could not leave the other one with android and ce was the only option I had.
Could it be that you have an S905X SoC in your box? Which dtb did you use under CE?
cat /proc/device-tree/amlogic-dt-id
There was not much point in upgrading too, but I gave it a try
And before that, which version was installed that worked?
Anyway, once I am done with le 11, I will try your image again.
If the LE11 will work on your box, there's not really much point in downgrading.
Unable to install XBMC.phyton 3.06 dependency (I think).
Python3 is only available from Kodi v19 (Matrix), only Python2 is available under Leia.
Please look for Leia (v18) compatible addons, because only those will run.
I jsut tried your s905 generic image on my mxqpro4k. It does not boot with any of the 3 relevant dtb files (gxbb_p200_1G_100M.dtb, gxbb_p200_1G_100M_RealtekWiFi.dtb and gxbb_p200_1G_mxq_pro_4k.dtb).
Did you use the toothpick method again? I saw that you tried an LE11 image before, but the new (mainline) and the old (3.14) aml_autoscript are not compatible with each other.
A simple question. What firmware should I download for an MXQ box (m201c) with S805, 1 GB and 10/100 networking?
Obs.: My Thanks to Google Translate.
If by firmware you mean an Android ROM image (either stock or custom), then you are in the wrong forum. If you mean the LibreELEC image, it's not a firmware, just an operating system.
So, If you're looking for the second one, you'll probably need the HD18Q LibreELEC image.
The problem is that no low-level USB functions seem to work at the moment.
Have you tried connecting a different type of USB device (e.g. flash drive) to the OTG cable? Because if that doesn't work either, then we have to check the problem elsewhere.
The interesting thing is that lsusb should also show the USB host chip (or the root hub).
If you unplug the OTG-cable and boot without that (empty first port), is the output still null?
my setup
Unfortunately, I don't have such a device, but are you sure this USB Y-cable with OTG-adapter is suitable for this purpose?
Maybe the middle two USB wires (DATA+/DATA-) are not shared in this Y-splitter (or I don't know, what is this), so I think this will not work.
I think the tuner only gets the power and that's it.
You should try adding a dedicated power supply to the 2nd micro USB port (I mean a real power supply, not a phone charger) and connecting the tuner to the first via OTG.
