Posts by dtech

Quote from Fartmaster5000

I'm trying to SSH using Putty but it's asking me for the host name. I named my "System Name" MBR and found my (local) IP address, but the following command doesn't work: ssh [email protected]

You don't have to type a command in PuTTY to connect, you just fill in a single input field, where you enter the IP address of the device you want to connect to, then press the Open button below.

If the SSH server is really working, it will first pop up the fingerprint confirmation warning, and after accepting it, it will ask for the username, where you just type root. If you haven't changed the password, the default password will be libreelec. And that's it. If anything doesn't work, then SSH server doesn't enabled, or the IP address is wrong, etc.

I'd be happy if we didn't make this an offtopic, these should be basic things for a unix system. If these things are not clear, then please let's not discuss them in this topic. These are completely general things, they have their own place on the forum here: General Support.

Quote from chewitt

The Amlogic vendor kernel has some drivers that assume an era-appropriate vendor u-boot is installed so it can probably be done with a little manual fiddling (which there are no guides for) to fix wrong-named boot files, but I guarantee that some drivers don't work right, and as the maintainer of the AMLGX image; this is not something we have any interest in trying to support.

Basically, I mean that the uboot under the mainline version is not made for Android layout, so the appropriate recovery functions are missing. I can understand this in the case of a development board, but in the case of a box like the WP2, which is originally built on an Android-based WeOS, it may not be suitable in the classical sense.

In such cases, I would draw the attention of users that the image written with emmctool may limit the full use of the box. And since the drivers for the built-in tuners will probably never be included, this is probably a dead end. That's why I don't recommend this emmctool solution for mainline kernel versions.

It also looks a bit like the installtointernal script that was previously rejected by official versions. This is now roughly the same, just in reverse situation. However, those images didn't even have a bootloader, because the factory one was still in use.

Quote from Fartmaster5000

Keyboard connected ... making progress .... but I pressed every button on the remote control (except for power) and it does nothing.

Please read and understand what I wrote:

Quote from dtech

You will not see any changes on the screen, but the following lines that are important to me will appear in the log:
kernel: remote: Wrong custom code is 0xHEXACODE

The pastekodi command will upload your log and generate a link where you can view it. It will contain what I need for the next steps.

Quote from Fartmaster5000

How do I run the "pastecodi" via SSH? You're not talking about setting the SSH password to that, correct?

The correct command is pastekodi, and please look it up in a search engine or AI for help using SSH, please don't expect me to explain everything to you.

Quote from Fartmaster5000

Turns out that my flash drive was trash, so I used a different one and it booted me into Kodi (I saw the LE bootup screen)!

Now for the big problem - the remote doesn't work! How am I supposed to set this up (and eventually use it)?

To complete the LE installation wizard under Kodi, connect a keyboard to the box. It is important to enable SSH during the process, because you will need it later. If you are ready with that, please press a few buttons on the remote control, then run the pastekodi command via SSH and copy the generated link here.

You will not see any changes on the screen, but the following lines that are important to me will appear in the log:
kernel: remote: Wrong custom code is 0xHEXACODE

Quote from Fartmaster5000

Followed the instructions; however, I had to delete the original dtb.img file because if I copy and paste it there and just try to rename it, it won't work (it gives an error that there's already a file with that name).

Then delete it first. It should work without deleting it and ask if you want to overwrite it, but it's irrelevant to the outcome now.

Quote from Fartmaster5000

Now, you mentioned the "storage" partition will first be expanded to the full size of the media - what did you mean by that? I still have over 300+ MB available.

You asked what you should see on the screen. Well, this operation, because that's what it will display while it's doing it.

Quote from Fartmaster5000

When I put this drive into the box, there's 3 USB inputs ... not sure if it matters which one I pick, but when I follow the instructions (turn it off, use the toothpick, plug it in and hold for 3-5 seconds), it doesn't "turn on". The light remains red. So I played with it a bit and tried using the toothpick, turning it "on" for 3-5 seconds, and it always goes to the Android recovery (doesn't matter if I do it for 3, 4, or 5 seconds). When I do it for 2 seconds, then it boots into the "Freedom Box" screen that I had seen before ... but I'm not seeing an "LE Boot Logo" or the Kodi initial Setup Screen. I'm seeing a "Freedom Box Setup" screen but that's likely because I factory reset it.

Did you unplug the DC jack at all? Just because the box turns on automatically after connecting the DC power.

Based on your description, you didn't do this, even though it is clearly described.

Quote

• Boot LibreELEC from your previously prepared bootable media:
  If you want to boot the device from your bootable media, you need to perform the toothpick method first:
  Disconnect the power plug, insert the prepared boot media, 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*.
  * If the Android recovery menu appeared, you pressed the button for too long.

Sorry, but I can't present a more detailed description than this, I think it's written in pretty kitchen language anyway.

Quote from wedok

Yeah i understand now, booting with box image and then write image to emmc.

Please note that since this does not contain the factory bootloader, the toothpick method and similar solutions will not work from now on, so if you write LE13 on the eMMC, it is not guaranteed that you will be able to boot older versions.

However, LE 9.2-LTS includes the factory bootloader, so the option to boot from an SD card still remains. The installation solution for this is different for eMMC, but I linked it above.

Quote from wedok

Btw, is an addon direct download possible for Legacy v9.2 (LTS) builds, like https://addons.libreelec.tv/, if yes whats the url?

Browsing these is disabled due to protection against search bots, but since they are built for a specific version by default, they are available through the built-in repo. Also, they are binaries, so they would probably not work under another version/distro.

Quote from Fartmaster5000

To make sure I get the procedure right, I have to download that USB Creator (Windows), install, then I need to select the file I want to download ... but which one do I want to download?

Then once downloaded, do I copy and paste the "raw" file onto the USB? Or how does that work?

You need the LE-AML USB-SD Creator version from here: https://libreelec.dtech.hu/LibreELEC-AML.…eator.Win32.exe

Then you need to select this:

After that, press the Download button, and when it's done, select your USB/SD media, then Write.

When it's done, you need to close the program, then open the media before releasing it, and copy gxm_q200_2g.dtb from the devices_tree to the root directory, and rename it to dtb.img, overwriting the one already there.

Quote from Fartmaster5000

Then once I put it in the unit and do the reboot / toothpick method, what should the unit / screen do if I was successful?

If you did it correctly, the storage partition will first be expanded to the full size of the USB/SD media, then after a restart you will see the LE boot logo, followed by the Kodi initial setup screen.

Quote from wedok

So i cant add: fw_setenv whereToBootFrom sdcard

This is a command that can be issued under LibreELEC 9.2.

Quote from wedok

Is there a trick to get the wetek tuner working in LE 13?

The built-in tuner and demod chips cannot be used under the mainline kernel because their drivers are not implemented.

Quote from wedok

And this dedicated wetek-play2.img is for installing to emmc?

The short answer to this question is YES. -> https://wiki.libreelec.tv/hardware/amlogic/wetek-hub-play2
But you have already tried LE9.0, LE9.2-LTS, LE13, CE, and on the eMMC still has WeOS. I just don't understand what your final goal is...

1. Is the DVB tuner important? If the answer is yes, please forget LE13, otherwise use an external tuner.
2. If you don't need WeOS on the eMMC, you can also install 9.2-LTS, the description can be found here:
   Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes
   (Please find the following section: "NAND install image for SD card".)
3. If you want to use CE, then you are in the wrong forum.

My LE9.2-LTS WP2 image supports the WP2 tuners as well, but Generic_S905 does not include the AVL6211 wetekdvb driver. For WeTek devices, the whereToBootFrom uboot environment variable specifies the boot media, so it can be overriding in the following way:
fw_setenv whereToBootFrom sdcard

Keep in mind that WP2 images do not contain autoscripts, but the Generic_S905 images do (which is also true for CE), so these nicely mess up the factory boot process, which differs from the standard Android boot order solution for WeTek devices.

Quote from UsagiPretzels

Somehow, the Avov remote for the box only makes red lights flash on my RCA LED TV and does nothing. I tried pressing a few buttons, but it didn't work.

It will happen in the log, and I would specifically expect these lines:

kernel: remote: Wrong custom code is 0xHEXACODE

Please follow my instructions, because without it we will only run unnecessary loops and will not make any progress in solving the problem.

Quote from UsagiPretzels

I also need help with the remote control configuration for the box's remote to configure.

If the image was successfully booted on the box, please press a few buttons on the remote control, then run the pastekodi command via SSH and copy the generated link here.

Quote from flydt

the 4th one, philips small remote control

Certainly not, because Philips does not use NEC code. If you actually tried that, I'm not surprised it didn't work at all.

Quote from UsagiPretzels

I also found out that this TV box had an Amlogic S805 SoC, which would be perfect for a LibreELEC Legacy v9.2 build.

It may work, although you will probably have to find the remote control configuration or make it a new one yourself.

First try to boot from SD card, using the toothpick method. You can find the description in the opening post of this topic.

Quote from flydt

today I try my 4 remote control by remote.conf, and get root cause why some remote no event in log

It's nice that you suddenly show 4 remote controls here, but which one is the one whose code I tried to implement for you under amremote?

Quote from TechmandanCZ

This results in segfaults, likely glibc incompatibility? Is docker supported for minix x8h-plus? As that's basically the only thing I need on it (tailscale+homeassistant+zigbee; it was previously working before updating it after a ~year)

You guessed it perfectly well:

Quote from dtech

Due to the switch to GLIBC v2.34, all binary addons have been rebuilt. The main version of the add-ons has been changed from v9.2.0 to v9.2.1, so after the system update, the binary add-ons will also be updated. In addition, the default transfer protocol in the repository has also changed from HTTP to HTTPS.

All addons should update automatically, but it seems that your system attempted to query the repo hash file before your network connection was established. At least, this is evidenced by the fact that the RTC date still shows 2019 at that time, because the NTP sync did not occur either.

2019-04-11 16:29:01.220 T:2891973376   ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
2019-04-11 16:29:01.221 T:2891973376   ERROR: CCurlFile::Open failed with code 0 for https://libreelec.dtech.hu/packages/9.2.1/S8X2/arm/addons.xml.gz.sha256:
2019-04-11 16:29:01.221 T:2891973376   ERROR: Open - failed to open source <https://libreelec.dtech.hu/packages/9.2.1/S8X2/arm/addons.xml.gz.sha256>
2019-04-11 16:29:01.221 T:2883580672   ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
2019-04-11 16:29:01.221 T:2891973376   ERROR: CRepository: failed read 'https://libreelec.dtech.hu/packages/9.2.1/S8X2/arm/addons.xml.gz.sha256'

You can manually trigger the repo update: Settings -> Add-ons -> Install from repository and select the LibreELEC Add-ons repository, and after pressing the menu button, select the Check for updates option.

After that, the updates will appear and all binary addon versions should have a 9.2.1 version prefix.

Quote from Fartmaster5000

Is there a sticky / walkthrough for how I upload this device from its current version (6.0) to the latest available?

Now I'm in a bit of a dilemma because from the information I found, the T8 Plus is equipped with the S812 SoC, and the T8 Plus 2 is the one with the S912. So which one do you have?

Edit: I assume that you really have a T8Plus-2 with S912, since Android 6 was not released for the previous model.

The opening post of this topic contains all the important information, from which I have highlighted the installation part. Otherwise, I highly recommend reading the entire post.

Quote from dtech

• Create bootable media (SD card or USB flash drive):
  To create bootable media you need to download the LibreELEC-AML USB-SD Creator tool. Select the file you want to download and click the Download button, or click the Select file button and browse the previously downloaded disk image (*.img.gz).
• Boot LibreELEC from your previously prepared bootable media:
  If you want to boot the device from your bootable media, you need to perform the toothpick method first:
  Disconnect the power plug, insert the prepared boot media, 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*.
  * If the Android recovery menu appeared, you pressed the button for too long.

The RESET (Restore) button is on the right side of this box, near the WiFi antenna, based on the photos I found.

Quote from flydt

pastekodi get URL of:

https://paste.libreelec.tv/pumped-shrimp.log

thank you

This would be good because it loads the config, but according to the log you didn't press any button on your remote.
Now I don't see the most important thing, because if there was a problem with the config, there should be a line like this:

kernel: remote: Wrong custom code is 0xHEXACODE

So I need a pastekodi that also shows the event that occurs when the buttons are pressed.
Sorry, but without this information I can't do much.

Quote from flydt

try many methods got from google, and found that, evey "key map editor" also cannot response with key event, as if there have some thing block IR remote control code

Please answer the question I asked: I created remote.conf for you a week ago, did you try it? If not, please do that first.
And if it doesn't work, please run a pastekodi and copy the generated link in your answer. Thanks.