my device have software problim 0x32030201 uboot/get result/diskinitial error can you help me pls
Unfortunately, this information is quite limited. At least it would be nice to know what kind of box you have.
Basically, it seems that your issue origins from the Android. You should restore the factory ROM first.
I successfully installed LibreELEC onto my MINIX NEO X8 PLUS today. The whole process went very smooth! I flashed the image onto an SD card and the MINIX booted into it without issue. I then used the installtoinernal command and that also worked perfectly.
The only real issue I see is the uboot power bug that's been mentioned already. I've enabled the "force suspend" workaround. This seems to suspend the device, but doesn't shut it down. Is there a safe way to shut down? I'm concerned that pulling the power cord could lead to data loss. Perhaps an SSH command that will help shutdown safely?
Thanks a lot for your work, dtech. I was able to salvage an old device from 2013 and make it modern and usable in my home once again. I sent a donation as a sign of appreciation.
Thank you for your donation. 
If you really want to unplug it, the safest way is to restart it and then unplug the power cord when the Minix logo appears. But I used an M8S in this mode for several weeks, and it also happened a few times that I also unplugged it from the outlet while it was in suspend mode. However, I have never had a data loss.
But this power workaround is only valid under Kodi. If you use the poweroff command under SSH, it will completely turn off the box.
I did try to extract .dtb file from stock android firmware and replace dtb.img, box boots but still no img.
Quote from the IMPORTANT NOTES - Please read them carefully before asking section of the first post:
- External DTB cannot be used with Meson8* (S802/S805/S812), because there it only takes into consideration those that are integrated into the kernel!
So even if you replace it, the kernel will ignore it. I need a full dmesg log, because I didn't find any wrong value in your uenv.
Yea my bad at calling it ROM. I boot from the SDCARD like everyone. The thing is that the remote isn't usable. I also inserted the remote.conf file in the files but nothing changed.
I interpret your first description to mean that your box is currently bricked. Then it seems that this is not true.
Now the question is, which image and which remote config did you use?
I recommend to try HD18Q image with FF00-Mecool (conf+xml) from this: http://libreelec.dtech.hu/remote.conf/.
Okay, I just found out this forum and I downloaded the ROM and booted it up from the SD CARD, the point is that neither the remote controller nor the power button work, is there any way to fix it?
model: k1 quad-core android DVB
amlogic S805
The LibreELEC image does not qualify as a ROM because it does not contain elements that standard ROMs. (eg. bootloader, recorery, etc.)
This is what you need to check:
Download latest Android KitKat 4.4.2 stock firmware for Acemax K1 TV Box «
Please a create an autostart.sh file with the following content:
fw_printenv > ~/downloads/uboot_env.txtCopy it through Samba to the \\<IP-of-the-box>\Configfiles\ and then restart the box.
After the restart please copy and attach the \\<IP-of-the-box>\Downloads\uboot_env.txt file to this topic.
My assumption is that there is an uboot variable for display that is causing the problem.
[ 33.788842@0] tvmode set to 576cvbs
The situation looks like you have an output only on the CVBS output instead of HDMI.
Try to extract and copy the attached file under Samba to this location: \\<IP-of-the-box>\Configfiles\, and then restart.
Hey there dtech , I cannot get LE working on my Minix X6 box (s805 amlogic). The systems start, I have acces to samba/ssh but no video output. It is just 'no signal'. Same was with Armbian Linux builds by balbes150 . I remember I found that on Armbian the 3.10.33 kernel had video output on my box and 3.10.108 did not, but I have no idea how to build kernel in libreelec. Maybe you have some builds with 3.10.33 kernels or have any clue why I dont have video output at all?
All patches are made for the latest kernel (3.10.108), so I would rather not undertake backward compatibility.
If you have an earlier working version based on kszaq's kernel, I would ask for a link. But I see it has never worked on this box before:
I may have found the error of the tuner: the wetekdvb kernel module is not loaded automatically at boot. 
This is the new snapshot version: http://libreelec.dtech.hu/snapshots/20220605/.
Tbh, i wouldn't bother. We make the mistakes, so you don't have to. Disgusting behaviour from the manufacturers not only did they stop supporting it, they took all the support forum and everything offline so you can't even grab old files. Really wanted their Ubuntu minimal. The box wasn't cheap either. I think someone managed to salvage the tuner to be used in other hardware. It's the only thing is was good for.
Coreelec do have working drivers for 9.2.8 if that helps?
I already have a WP1 and a Core, so a WP2 can really fit next to the others. I've modified quite a lot of things in the v3.14 kernel, but in a pretty different way than the CE team. Without "trying", the story is not that simple. And I like to check in practice what I made. 
dtech I have another WP2 box lying unused at my parents in the UK, so if you don't find one via eBay I can always post that one to you when I visit them in mid-July.
Thanks chewitt. I managed to find one, now the bargain is coming. If by chance this fails, I will tell you right away. Thank you very much. 
Hi, i see you have not made a wetek play 2 build but did see you made an ad hoc for a user. Is it safe to assume that snapshot 3 is the one that should be used?
It hasn’t progressed since the last snapshot above (20220504), but since you are the third to find me with WP2, now I’m really trying to get one from somewhere (at a reasonable price).
I looked it back, for an earlier conversation, and if I saw it correctly, you have an M8S box. Somehow you need to determine exactly what variant you have, this would require a good quality photo of the PCB.
For example, this is my own:
It doesn’t explicitly run with any ROM, just its own, which I also found pretty hard to find in the past.
UPDATE2: A fresh start with a new image solved all issues!
Running out of free space can produce a variety of errors. I'm glad it's resolved.
Good thing you remembered all those details, because I remembered none
I remember we talked about it, but due to the specific data, I also looked back in this topic.
Does anyone know if the black mxq supports 5ghz wifi? If not, how about the mxqpro 4k.
Different manufacturers equipped their devices under the same name with different wifi chips, so your question cannot be answered.
But since we have discussed the wifi chips in both of them before (in this topic), I can answer directly.
Your MXQ (S805) has this:
Bus 001 Device 003: ID 0bda:0179 Realtek Semiconductor Corp. RTL8188ETV Wireless LAN 802.11n Network AdapterRTL8188ETV -> The answer is that it is only capable of 2.4 GHz (802.11bgn).
Your MXQ-4K (S905) has this:
...
configuration: broadcast=yes driver=rtl8189es driverversion=3.14.29 firmware=N/A ip=192.168.1.136 link=yes multicast=yes wireless=IEEE 802.11bgnRTL8189ES -> The situation is exactly the same, the only difference is that this chip connects to SDIO instead of the internal USB line: 2.4 GHz only (802.11bgn).
So, if you are going to install a wifi router (or AP) that only works in the 5 GHz band, it will not communicate with any of them.
Neither my friend. I wonder if it is due to crazycats tuner driver. I saw other img. that have it, but this doesn´t
It is no coincidence that it is disabled. The crazycat and dvb-latest driver packages cannot be simply enabled or disabled. To make these work with my other images (including kernels 3.10 and 3.14), I had several weeks of work involved, including testing with various external USB tuners. The WP2 internal dvb driver was not originally included in any of them.
However, I am still waiting for your system log. I want to help, but that only works if I get answers to my questions.
The link in the first post no longer works.
Is there no other way where it is not necessary to open the box? Maybe an USB to serial converter from the USB port of the box into the serial Port of the PC?
Only an Amlogic SDIO debug board would be an alternative to the physical UART port, but it also requires a TTL adapter.
Round #3: http://libreelec.dtech.hu/snapshots/20220504/
If the tuner doesn't work with this either, I really have no further idea without the system log.
Unfortunately now i am having a new problem. My box is booting with the image.
it is preparing the storage partition and rebooting fine again but then it stops at the Libreelec splash screen and not booting into Kodi.
Kodi is als not completely installed on the storage partition so i don't get any logs. If i put your original tar file into the update folder,
it is installing your system and after the reboot Kodi is starting up like it should.
How can i fix this trouble?
You will need an USB-to-TTL adapter for deeper analysis.
