Posts by dtech

Quote from Fartmaster5000

dtech - i did the pastekodi after pressing buttons on the remote. Then i provided the link output. What do i do next to get the remote to work?

Where is the link?

The previous one doesn't show any key press event, and the first one was almost full of sshd errors. Apart from that, you don't need to do anything else for now, I'll try to find a compatible remote control config for you.

But for this I need that log, which contains at least one line like this:
kernel: remote: Wrong custom code is 0xHEXACODE

Quote from Fartmaster5000

So what is the next step to get the remote to work? dtech

Last time we were here, this hadn't happened yet:

Quote from dtech

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

And please don't post twice in a row, because I only get notified about the first one, and that's more than enough.

Quote from Fartmaster5000

Done. Says "Log files pasted to https://paste.libreelec.tv/saving-sawfly.log"

The installation wizard probably didn't complete properly, or this USB flash drive is also junk. The log is full of entries saying that the ssh key generation failed, so it tries again, but it can't be written.

There would be a workaround, but the easiest is to rewrite the image to the flash drive and start over. However, the toothpick method is not necessary again.

Please try uploading the log from the LibreELEC settings this way:

This is completely equivalent to the pastekodi command.

Quote from Fartmaster5000

LibreELEC is running and i am trying to SSH root@ipaddress with SSH definitely enabled during the LibreElec setup.

I would like to ask you for some photos based on these:

1. Settings -> LibreELEC -> Connections:

2. Settings -> LibreELEC -> Services (the focus is on SSH):

3. Does it respond to a ping sent to the IP address?

4. I would also like a screenshot of the filled state of your SSH client before connecting, like this:

Quote from Fartmaster5000

I did exactly what you said - but it will not connect (Connection Refused). I did some more digging and it looks like the Android Box's core OS has to have SSH enabled, but when you're doing this "boot method", you don't have access to it. Sounds like side loading / adb might be the only way to load everything.

As noted above, one of the key concerns I have is knowing if LibreElec is a ROM that will overwrite the stock ROM so it boots into Kodi by default. If I need to do the toothpick trick every time and reset everything, that is not a solution.

The LibreELEC image is not a ROM, it is just an operating system image that contains the kernel, root filesystem and dtb. If you run it from external media, it will not overwrite anything. The toothpick method only loads the autoscript on the card, which allows the bootloader to boot the OS from USB and SD card instead of eMMC, if it is connected, otherwise it will still boot from eMMC.

The toothpick method only needs to be done once, after that it will always be able to boot from external media, unless Android receives a master reset command, because that can overwrite the boot script changes. Also, if I may suggest, try using an SD card instead of a USB flash drive, because the USB is much more problematic.

The basic problem with your description is that it is not clear whether LibreELEC is running at all when you try SSH, whether you are trying with the IP address of the box, whether the network is working on the box at all, and whether SSH is definitely enabled or not. Instead, you mention things like adb and sideload, which are absolutely not needed for LibreELEC.

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.