hopefully there will be a post in there with the file I need
If nobody has done the work for you already, just write your own. It is easy and you can then upload the remote.conf you create to the remote.conf repository and help others that might have the same problem 
But what if I install TWRP? Is it possible to force reboot in TWRP in case, let's say, I brick the libreelec in nand and then reboot from SD?
I'm not sure why some feel the need to install to internal, as LE works flawlessly from SD / USB without any risk of bricking anything (and also leaving the original Android OS available as an option). There is no noticeable degradation of speed and the extra cost of a USB / SD media is negligible.
However, to each his own, and if your choice is internal memory then the following facts have been repeated several times throughout these Amlogic build LE forums;
You cannot install TWRP if you install to internal.
Provided that the box is able to boot from SD you can use TWRP by placing the correct TWRP image (renamed to recovery.img) and the native Android dtb image on an SD card and then reboot, using toothpick method or issuing reboot recovery command via SSH.
After flashing the last build for the first time to internal memory my Beelink MX didn't react anymore.
Had to burn the image to SD card using Rufus. After that I could install it to internal again with the command.
I thought (for the first time to internal) the recommended method was to install to SD and then use the Installtointernal command from there. 
Funny thing is i used my TX5 Pro remote.conf and every button on that remote worked including the power.
Replace the factory code in the TX5 Pro remote.conf with the one for this current remote and see if that works
Scratch that (haven't woken up yet)
Make your own remote.conf for the new remote (It's easy)
I am pretty sure i will need to extract device tree from Android.
Outside of getting it from seller is there an ADB command i can issue ?
Is there no root access in Android?
If so, there are several excellent root explorer & partition dumping Android apps available 
Can you please give me a hint how to install to internal.
The installtointernal command is well documented in these threads.
With TWRP?
You do not use TWRP to do the install. You can use TWRP afterwards by placing your android dtb and the correct TWRP build on an SD card and issuing reboot recovery via SSH.
Of course, once you have made a successful TWRP backup it can then be restored via TWRP
Since 8.2 smb mounts to my windows10 machine won't work anymore.
I don't use Samba shares myself, but I'm pretty sure I have read here (numerous times) that the newer builds require a Samba password.
If you are not using Samba passwords then the obvious fix would seem to be to start doing so (or use a different method of file access by your media box)
It appears to be using ASIX AX88179 chipset and LE eats it like a charm.
You obviously will be restricted to USB 2 speed which is nowhere near Gb maximums ( I don't think 905/ X support USB 3)
Then again, If it's enough to solve your buffering issues - job done! 
Error in mount_storage: mount common: could not mount LABEL = LIBREELEC_DISK
Ensure the SDcard is of adequate size (and type 10)
Check the label of the SD card in a PC (should be LIBREELEC). If not, re-make the SDcard
or
Use linux OS to correctly name the partitions on your SD card (LIBREELEC for boot partition & LIBREELEC_DISK for storage)
or
Make an SD using an earlier version of LE and then upgrade this SD to the version you want
Is 8.1.1 a test build?
I think these are all test builds
Seriously, just read the goldmine of info that is available (in these threads for sure, but also in other forums)
You can create a remote.conf for any remote you care to use.
Avoid asking for everything to be handed to you on a silver platter.
The only way anyone ever really learned anything is by researching for themselves.
Try it, one day you might be able to help someone else out (which is the point of these type of forums)
People that have discovered the answers you seek do, eventually, tire of keep answering the same questions (again and again) for those that won't attempt to read what is already available
Just applied this update. No obvious issues on any of the boxes so far
So, to sum up, for same usage : good cheap box for android/kodi but bad box for LE, no matter.
If you're are happy with the performance of Kodi for Android, it doesn't really matter if your particular box can run LE reliably or not.
If it's working to your satisfaction on Android, use Android.
The big problem is that LE is unstable . . .
The big problem is the NEXBOX. They've been noted as cheap and nasty since way back.
My experience has been that LE is extremely stable if you pay a few dollars more for a more reliable box
Device tree is updated only during update process.
meadrocks So put it in /storage/.update along with the kodi update file you last used
Many thanks kszaq, as always
I think the user originally mentioned he was using SCP to connect - which is SSH and NOT samba.
But then asked (in response to frequenzy's suggestion/advice "enable samba, then transfer the file.") . . .
Quick tip if any...how do you connect to Samba from a PC?
Receiving the reply. . .
If using Windows, use Putty.
Which, as Forage correctly pointed out. . .
Putty is for SSH, not Samba (i.e. Windows file sharing)
The power suspend does not fail for 95% of the users. It works fine here.
Perhaps you're in the 5% bracket? I doubt that figure was simply plucked out of the air 
