As we all know, s812 can play no more than H265 4k@24p.
In my case, I can play H265 4k@50p, but hdmi maximum resloution is 4k@24p.
The limiting factor is mainly the HDMI 1.4. So if a higher frequency came out of it, it might not be stable.
So far, I haven’t been able to figure out how to add custom resolutions because 3840x2160p isn't listed either.
I'm glad the m201d image worked. 
Unfortunately, many manufacturers have "lied" to the 1GB so that the Android code has also been modified to show a false value.
Just so I understand correctly, you're saying that swapping the dtb around doesn't work because the unit only checks the device tree that is baked into the kernel? If I have that right, I wish I had known that about three days ago. LOL. Oh well, live and learn.
I learned from the case, so I rewrote it in the lead post. 
IMPORTANT NOTES - Please read them carefully before asking:
Unfortunately, there are plenty of clones from M8S. If the M8S+ image doesn't work on your M8S, try this one, if it's a 2G/8G model:
Index of /3rdParty/S8X2/Universal-n200-S812_2G-AP6330/
... or MXIII image, if it's a 1G/8G:
Index of /3rdParty/S8X2/MXIII-S802_1G-AP6330/
(Whether S802 or S812 SoC is included does not matter at this point.)
1. What program do you use to write the "img.gz" file to the SD card?
2. Have you also tried the m201d image?
Because I have read in several forums that the V3_1 board is also suspicious that it’s only equipped with 512MB of RAM.
3. Replacing the dtb with the meson8 kernel is not a solution because it can only read the dtb integrated into the kernel.
Quote from the notes section of the first post on this topic:
External DTB cannot be used with Meson8* (S802/S805/S812), because there it only takes into consideration those that are integrated into the kernel!
Try the m201d image with the toothpick method first. If that doesn't work, try getting a smaller SDHC card.
What does survive reboot is: during a playing video -> Setup -> Video settings -> stretch to 16:9
Then the video looks good, but gui is still on 4:3 mode (ugly stretched).
If this option is set to a value other than normal, it will also affect the calibration and will be completely bad.
So, please do not use manual aspect ratio override, because calibration alone will solve this. Calibration will set the video and GUI in sync.
For us, that’s the point now, because that’s how it can’t happen that the video is good and the GUI is bad. Either both are good or not. 
Anyway, I managed to find a solution to the problem, though not the way I thought.
The disp_cap file needs to be edited. Inexplicably, the resolution is not recognized if it only includes 576cvbs:
But, if disp_cap has been edited, it will already appear:
(My display is already pre-calibrated, of course it won't look like this on your side in the first round, the edge of the image will hang over everywhere.)
If you see the resolution here, the calibration data will also be saved and will not be lost after a reboot.
Contents of the new disp_cap file:
480cvbs
576cvbsAnd that's all. 
If you have edited the file, you will need to restart the device and then you can start the calibration, which will not be lost now.
Be careful not to accidentally switch to 720x480i60hz if possible, because I don't think European CRT TV with 60Hz will be able to do anything.
Sorry, you are right, I really messed up the beginning of the description because it's the same as yours.
1. TV settings standard 4;3 -> the gui itself shows itself to be 4:3 which is perfecty fine, but not widescreen (black bars left / right)
2. TV set to 16:9. The gui ratio now looks bad, with everything horizontally stretched. (but no black bars)
So far, everything is the same as what you described...
Did you give up at this point? Just because the setting starts from this point.
You will then need to start a 16:9 aspect ratio TV stream and begin calibration during the video:
Setup -> Video settings -> Video calibration
The setup menu is half hidden in the lower right corner (gear icon).
The only problem is that the 576cvbs mode is not recognized by Kodi properly and thus does not save the calibration into guisettings.xml.
So after a reboot, the calibration will be lost for now. But I’m already on it to fix this bug.
A temporary solution is to manually add calibration data:
...
<resolution>
<description>720x576 @ 50.00i - Full Screen</description>
<subtitles>519</subtitles>
<pixelratio>1.442886</pixelratio>
<overscan>
<left>30</left>
<top>21</top>
<right>688</right>
<bottom>555</bottom>
</overscan>
</resolution>
...Do you have any idea what could be the problem?
Did you stretch it from 4:3 to 16:9 with the video calibration? It shows an adjustment of 1,4.
Without video cal, did you not have 4:3?
Fixing 4:3 to 16:9 with video calibration,isn't that "wrong way" to do that?
Okay, I'm trying to say in order...
The "disp_cap" contains 576cvbs only!
I don't know if this is a good solution, but it would be right for me.
Gui settings aspect ratio still mangled at wrong res.
After the last step of the calibration (pixel ratio adjustment), the GUI will also be displayed in the right aspect ratio:
How can I put in a custom resolution in Libreelec?
The problem is not the custom resolution, but the fact is that there are no signal via composite output if the resolution set other than 480* or 576*. At least that is what I have experienced.
Well, I tried CVBS and I have nothing wrong with it, I just went through the calibration operation.
Video calibration -> It will fix overscan and pixel aspect ratio:
Video settings -> I didn't have to change anything:
TV aspect ratio (Standard -> 16:9):
Has bumerc sent you a firmware link yet?
Stupid question, but I have to ask:
After you have connected the device to USB and it is detected by the Buring Tool, do you then plug in the 12V power jack to the device or not?
Because if you don't, that will be the problem. Maybe your DIY USB cable does not provide enough power to the device for the flash operation.
However, if you plug in the jack and the error still persists, the quality of the contacts will cause this problem and a new USB A-A cable will be needed.
Okay, now I see that this bootloader isn't good, because it's made for a 2x1GB memory layout version and your version is 1x2GB.
Only LPDDR and its clock are correct, but the allocation is not.
Which firmware was last tried?
Is this status based on what I sent earlier (#2), or did it happen after the image sent by bumerc?
Why not put 576i wdescreen in there? hmm.
Is the 576i not the same as the 720x576i50? Because its ratio is still 4:3.
The correct resolution for 16:9 would be 1024x576i50 if we do not reach the height value, but I don't think it will provide a signal with this resolution on CVBS. A try will tell you.
I’d like upload ap6335e_nvram.txt late. Hope it will be hopeful
Thanks, but the file is already included in the brcmfmac_sdio-firmware-all-aml package as well.
I'll check it out, but I would ask you for a little patience, because an HDD from the RAID1 array died on my server yesterday.
Until it is replaced and re-synced, I don’t want to build a new image.
(It will still be an emergency intervention, mainly because of the virtual machines and I don’t want data loss.)
At the same time, I predict to everyone that http://http//libreelec.dtech.hu/ and my LE repo will not be available for a couple of hours on Saturday.
Confirmed with a LCD TV using the composite input. It is the same. We have a 4:3 output on 16:9 TV.
Well, I may not have anything to suggest.
I have tried to look for this error here in the forum or on the internet only in relation to Kodi, but I did not find anything relevant. 
Okey, Try this dmesg.txt
That's good, thank you. I noticed something...
The image for M8S+ uses a different nvram configuration (ap6335_nvram.txt) than datrh's X8-H Plus image (ap6335e_nvram.txt).
However, my X8-H Plus image statically loads "ap6335e_nvram.txt", so I don't really understand why it freezes. 
Okey, this dmesg from datrh version.dmesg.txt THX
Unfortunately, startup events are now completely missing from this log.
The first line is this:
[ 665.570576@0] remote_send_key sleep:0Please send one immediately after start-up, before pressing any buttons on the remote control.
I don't suppose your build would include the SPDIF multi-channel audio device (last seen in official LE in 8.2.5); [8.95.3 Wetek Core] Missing multichannel audio output ????
My build is based on 9.0.2, so if it didn't work there, my image probably won't work either.
But I never had a WeTek Core, so I can't test it. I made the image on request, but it seemed to be a waste of time.
I would also like a dmesg from the datrh version.
Unfortunately, newer LG OLED TVs no longer have any analog inputs installed, so I can't try it now.
But this weekend I will also try the CVBS output with another TV. (16:9 LCD with composite input)
It is only a help for those who want to restore their device. Fantasies about advertising are superfluous here my friend.
Okay, but then I don't understand that if we already have a working firmware specifically for this box (KI PLUS S905D 1G 8G DDR3 LR), why would you suggest another one that was made for a completely different box?
At the moment, it seems that there is something wrong with the USB A-A cable and not the firmware is causing the flash error under USB Burning Tool.
I think the firmware you are proposing should remain Plan B for now, and let's not start with that first. At least that's how it makes sense.
Amlogic burning tool still showing error with all images, also yours.
[0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error.
in UART unchanged : GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;CHK:AA;USB:8;
I think you should get a factory USB A-A cable instead of a DIY cable.
The ATV ROM I posted already includes the correct WiFi driver and fw. 1g eth has nothing to do with installation for the time being, the TV box would also work without eth.
I don't care which firmware can hudyj flash to the device, the point is that EVERYTHING should work on the box. (Ethernet too!)
He could try to install this FW first via the sdcburn method, it is for lpddr3 devices. At least the bootloader should be running. I could add 1G dtb later..
Please keep in mind that this is the LibreELEC forum, so this is not the place to advertise your own Android creation.
