Posts by dtech

Honestly, I don't think I've ever tried USB booting on any of my devices before, but I did it now.

Well, neither on the S805 nor the S812 devices work. Has anyone had any success at all from USB on Meson8*?

Quote from hiep.ton

I have an Amlogic m201 (S68) with its detail information below (I ran CPU Z app to get this information):

Kernel architecture: armv7l

kernel version: 3.10.33 (20160924)

build id: KOT49H.20160924 test keys

Java VM: Dalvik 1.6.0

Android version 4.4.2

API Level 19

Model: SBOX (m201)

Manufacturer: MBX

Board: m201

Hardware: amlogic

RAM: 831 MB; Storage: 5,09GB

cores: 2

Architecture 2x ARM cortex-A5 @ 1,54 GHz

version: sUp1

GPU Mali 450 MP

Display More

I think you need the HD18Q image, not the m201d. The problem is that I still have no idea what kind of device you have, because booting from external devices requires the toothpick method. However, I have no idea where the reset button is on an unknown box.

Can I ask for some photos of the box, including the bottom and the back?

Quote from hiep.ton

Hi Dtech,

Could you help:

1. Create an update package for MXQ m201d (512M/8G) a.k.a. "all black" versions with 512 MB RAM only? Because my Android box has only 512 MB.

2. Create an installation package from USB for MXQ m201d (512M/8G) a.k.a. "all black" versions with 512 MB RAM only? Because my android box has only USB ports, no SD cards. Or could you show me the link, commands to boot libreelec from USB?

Thank you very much in advance!

May I know what device you have?

Quote from jim_p

Is this correct? If so, how can I add some boot parameters to it?

The cmdline parameters are hardcoded into the kernel, namely by the kernel config:

LibreELEC-AML/linux.arm.conf at master · dtechsrv/LibreELEC-AML

'Just enough OS' for Kodi for some Amlogic TV boxes - LibreELEC-AML/linux.arm.conf at master · dtechsrv/LibreELEC-AML

github.com

But kernel also loads the initargs variable into the cmdline, so if you add what you need, it might work.

Read initargs variable:

fw_printenv | grep initargs

You can change it with this command:

fw_setenv initargs "... variable=value"

The ... means the original value, the whole string returned by fw_printenv | grep initargs.

I think what comes next is quite clear: variable=value.

Quote from jim_p

Can this run, and return the right result, on android too?

I have no idea, I don't even know the time, when was the last time I ran Android on a box.

mgear

Please log in to your box via SSH and try this:

REMOVED CODE

After that you need to reboot and check if there is any change.

Update: The new v9.2.8.5 image includes an updated tz package (2022a).

Quote from jim_p

Can I run that and boot from a usb device?

Theoretically yes, but practically uboot dependent because not all boxes can boot from USB.

Please try this workaround:

Post

RE: Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

[…]

Unfortunately, if a storage device is connected to an external USB (external HDD, flash drive, etc.), it would try to boot from there first.

If you need to ignore startfromext, you need to set this:

(Code, 1 line)

And then reboot. If all goes well, it will no longer try to boot from an exernal device (not even an SD card).

dtech

September 14, 2021 at 2:14 PM

Quote from jim_p

There are no devices connected to it. Just the hdmi cable and the power supply.

Some log file would be great. Anyway, is the LE running from the SD card or NAND?

Quote from jim_p

Does anyone use the all black s805 mxq? I did the upgrade to 9.2.8.4 today and I could not help but notice how much time the mxq logo stays on the screen while booting up. It is shown for like 1 minute! After that, le takes less than 30 seconds to boot to kodi.

If you use any USB device, this can happen because it will also try to find bootable devices there, even if there is only one mouse plugged into the USB.

Quote from punter

hi dtech

I've got a F2 A95X with s905x

I tried your image for MXQ-4K but it just hangs at the A95X boot image

any ideas to get it working?

cheers

The v3.14 kernel I use does not support the second-generation Amlogic S905x SoCs (G12A), and your device has an S905X2.

I don't know how the LE11 stands in support of these SoCs, I think you can inquire here:

Thread

Official LE11 Test Images for Amlogic (Kodi-20)

Discussion thread for the official testbuild from https://test.libreelec.tv .

These builds are build against https://github.com/LibreELEC/LibreELEC.tv , no additional changed included.

CvH

August 28, 2020 at 11:13 AM

Quote from jim_p

Thank you I will try it once I get the tvbox on my hands. However, the owner will try it himself first and may not send it to me

Is there a procedure that must be done so as to boot it from the sd card?

It depends on the box, but usually the standatd toothpick method is required.

Quote from jim_p

Ok, let me make the question straight: can I install any of the available libreelec-aml images to it?

My suggestion is to use the MXQ 4K Pro+ image with this remote configuration:

http://libreelec.dtech.hu/remote.conf/4040-M8S/remote.conf

(At least based on the photos on the web, this is its remote in principle.)

Quote from jim_p

A friend asked me if there is anything he can do to revive a mini m8s II that he has. All I know so far is that it uses a s905x soc, 2gb of ram, 8gb of storage and 100Mbps of wired ethernet connection.

It should be something closer to the current state of the box, and "revive" should also be interpreted because the meaning of this word is quite context dependent.

LibreELEC v9.2.8.4 (2022-06-25) has been released for S805, S8X2 and S905x devices.

• WeTek_Play, S805, S8X2, S905: add SCSI generic support for USB optical drives (Direct I/O),
• WeTek_Play, WeTek_Core, S905/WeTek_Play_2: restore amlpkg creation for WeTek devices (zip),
• WeTek_Play, S805, S8X2, S905: fix h264 aspect ratio issue for broadcasts on PAL SD and HD Lite resolutions,
• S905: add SoC model name and family to cpuinfo,
• S905/WeTek_Play_2: add support for the WeTek Play 2 (GXBB) box,
• S805/HD18Q: non-functioning S/PDIF output fixed in dtb.

For download links, please check the first post in this topic: #1

Mirror (GitHub): Release LibreELEC v9.2.8.4 for AML S805/S8X2/S905 (2022-06-25) · dtechsrv/LibreELEC-AML

Notice: The S8X2 group also includes WeTek_Core.

Quote from richard_zorge

If I will install your LE build on my Wetek Play 1 would I be able to boot enigma2 from SD card? (I have official 9.0.2 LE in nand now but I cannot install anything from repos now)

Of course, the option to boot from the SD card will not disappear after the image is installed.

However, updating WP1 via tar is a bit tricky, but there is a workaround:

Post

RE: Wetek play 1 cant update to 9.0.2

Hi, is there anyone willed to write howto get the wetek play 1 updated to Libreelec 9.0.2? Unfortunately it doesn't also work for me with the .tar in update folder. It runs during the next boot and says libreelec 9.0.2 successfull installed and reboots again, but then it's again only 9.0.1 and Kodi 18.1 on the device.

Unfortunately there is no real alternative to wetek play1with dual dvb-s2tuner.

edit: For those who still struggle with the update. The trick is login as root then:

(Code, 2 lines)

…

suppenkasper

February 28, 2020 at 5:16 PM

Quote from itsnikolasgr

Hello again, I'm the guy with the Acemax K1 TV BOX. I have managed to fix the issue with the remote controller, but unfortunately I ran into a different problem. I don't have an audio playback. I have plugged HDMI, by hardware everything is working fine. I also checked every single audio output that is available and still no solution. Do you have any suggestions?

I compared the factory dtb of the KI T2 and my version of the HD18Q, and there is no entry in the audio settings that would justify not having audio over HDMI. Also, in my version, the analog audio output and S/PDIF should work. So without the logs, I don’t really know what the problem might be.

Quote from asif

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.