pls help
Try to write the image to another SD card, because either the file system or the card may have been damaged.
Leia 18.1 on Matricom device.
All Add-ons failed to install and/or update.
I think this is what causes the error:
Posts by dtech
-
-
kszak
His name is spelled correctly: kszaq. However, hyp3r wasn't specifically looking for the image you linked. The only one that had AP6210/AP6212 wifi+bt is specifically the MXQ image.
The last kszaq images I saved can be found here:
Index of /_TEST_/kszaq-archive/
However, since kszaq's repo is no longer available, the LE addons cannot really be installed.
-
1.Yes, when i press on it,nothing happend.
Because it's a direct link, so try this: Right click -> Save as...
-
http://libreelec.dtech.hu/_TEST_/kszaq-archive/LibreELEC-S905.arm-8.2-8.2.3.1.img.gz
Are you looking for this image?
The dtbs are available here:
However, kszaq's LE repo is no longer available.
-
I have bigger problem now.
I made contact with reseller, they said that MXQ 4K 5G have Allwinner H313 chipset.
Is there any hope for libreelec or i should send back this product(and look for amlogic = X96mini, de X96Max of de X96 x4)?
As I saw, there is no support for the Allwinner H313. I also can't recommend a box, especially not one that I've never had either.
-
Yeah,the original MXQ(5G)...only do not know what version Amlogic or else.
Have reset button but will not get into dual boot.
Evry time boot into normal no metter how long reset button is pressed.
MXQ(5G) -> It is not an exact type, just a fancy name. However, I cannot recommend a dtb without the correct specification.
By the way, there are actually some of these that do not even contain an Amlogic SoC. (e.g. Rockchip RK3229)
You should somehow find out what it contains and how much RAM is in the box.
-
MXQ just arived...
Except Libreelec image, do i need to copy "tree" dtb to?
Is it possible to know the exact type? Unfortunately, the MXQ is a bit short. (The original MXQ is just an S805 box.)
-
Something went wrong...i`m not able to boot into libreelec any more from sd card.
WeTek images do not need aml_autoscript, but standard images need it. However, this only runs if you use the toothpick method:
Start LibreELEC from SD card:
If you want to boot the device from an SD Card, you need to perform the 'toothpick method':
Disconnect the power plug, insert the prepared SD Card on, which the image file is written (img.gz), and then press and hold the reset button. Reconnect the power jack while holding down the reset button, then release it after about 3-5 seconds.
NOTICE: If the Android recovery menu appeared, you pressed the button for too long.The toothpick method only needs to be run once, but it is an important step because it sets a bunch of uboot variables, which are needed to boot LibreELEC from SD card or USB (and if it can't find them, it will boot from eMMC/NAND automatically). However, the aml_autoscript of LE8 and LE9 are not compatible with each other, so if LE8 was installed earlier, this may be the reason why LE9.2 does not start. But the toothpick method will solve this problem.
WeTek devices do this whole method differently: Power button -> whereToBootFrom uboot variable. This is one of the main reasons that WeTek images are really only for WeTek devices.
-
,
What does that mean again?
-
I downgraded to 9.8.2.5 but the problem with wrong time is continues.
As I can see, the problem is not with the new version, so there will be an external problem in the background.
Unfortunately, the real information content of your messages is very low, so I will not be able to help you effectively. You still didn't post what kind of device you have. Some boxes also have a 3V lithium battery, which if discharged can confuse the RTC.
Also I notice that some addons not working anymore, and some new updates fail to installed.
First of all, if you are trying to install/update from an external repo, you need to find the distributor with this error. I can only help if you only get an error when installing/updating from the LE repo, but there have been no updates recently.
Make sure you are trying to install packages for the Leia version (v18) of Kodi.
-
Where I can find the older image ? I only can see 9.2.8.6 version
Index of /images/3rdParty/ARCHIVE/
Notice: I only know from the kernel compile date that you are using the n200 image, because you didn't write your device type at all.
-
Do i need to take a photo of remote?
If it is different from the picture below, I would like to ask you for it.
But, if it matches, it's unnecessary. I have never met this type before.
-
1. If u can provide info where to look, gladly will do.
Wait a sec... What you marked with 1. doesn't affect you, only the part of my previous post after 1234LP concerns you.
If you really have the box under the link, with the same remote control, then I can't recommend a remote.conf, because I don't know this remote control.
-
You should try a downgrade to v9.2.8.5. If the error was really caused by the update, then the error should disappear with the older image.
I would suggest a different combination, and preferably use a WeTek image only for WeTek devices.
Recommended image: MXQ-4K-Pro_2G, dtb: gxbb_p200_2G_1Gbit.dtb.I can't provide a remote control configuration until I see what kind of remote control it came with from the factory. Can you send a photo?
Edit:
Do you have this device? -> https://www.gearbest.com/tv-box-mini-pc/pp_555824.html
-
It seems strange to me too, basically it synchronizes with NTP immediately after the DHCP lease on my M8S+:
CodeJan 01 01:00:17 M8S-Plus connmand[2191]: eth0 {add} address 10.60.0.55/24 label eth0 family 2 Jan 01 01:00:17 M8S-Plus connmand[2191]: ntp: adjust (jump): +1666538362.234929 sec Oct 23 17:19:39 M8S-Plus connmand[2191]: eth0 {add} route 10.60.0.0 gw 0.0.0.0 scope 253 <LINK> Oct 23 17:19:39 M8S-Plus connmand[2191]: eth0 {add} route 10.60.0.1 gw 0.0.0.0 scope 253 <LINK> Oct 23 17:19:39 M8S-Plus connmand[2191]: eth0 {add} route 0.0.0.0 gw 10.60.0.1 scope 0 <UNIVERSE>But this (line 2) is missing from your log. What regional settings are you using?
-
if possible you can share TVH on your website. Currently, the link is not working
The previous link is no longer live because it was added to the repository in the meantime. If you use my build, you should find it here:
Add-ons -> Install from repository -> LibreELEC Add-ons -> Services -> Tvheadend Server 4.3 (Alpha)
-
these appear on your site that is currently down
It is now available. There was an error with the ISP again. The simple reason: the "big fish" has acquired the "small fish" and now they are migrating the entire network to their own existing one. There have been problems for months, but they promise that it will finish soon.
I can't find the third party images on the github mirror.
Could you pass me the link to download them or upload them to github?
I didn't plan to upload the 3rdParty images to GitHub, because they need a lot of space together.
If the server is unavailable, I recommend the Wayback Machine.
I wanted to try to see which of them would go well with my tronsmart s89h, since I tried with the M8S PLUS but it does not raise the wifi or bluetooth.
You need to try the Universal k200 image on your box, with this remote.conf.
-
Thanks for adding image for Odroid C1+. It boots without any issues.
Is it possible to install transmission client? I understand that these old kernel devices lack docker support but maybe there is another way like entware installation. Or is there still has working add-on for this.
Docker does not work at all on Meson8* boxes with the old 3.10 kernel, so you should find or build a native transmission binary package.
Our long-standing project policy refuses to build and publish bittorrent clients, so unfortunately I cannot help with this request.
