Why my wetek hub boot only from generic box img? This version https://releases.libreelec.tv/LibreELEC-AMLG…etek-hub.img.gz doesn’t work.
It does work, but it's a board image designed to be installed to emmc (overwriting Android). The box image is the correct image to use if you're booting the device from an SD card. Read: https://wiki.libreelec.tv/hardware/amlogic
The dmesg log looks fine, the WiFi NIC is probed without errors. Some German users (a guess based on your name) need to have the 80211 regdomain configured in LE settings (under Network) before networks can be seen. See if setting to 'DE' makes a difference?
In the absence of a debug log it's hard to comment, but some add-ons are geolocked and only accessible to users in specific countries; is my guess at the probable cause. If the add-on requires a subscription (and some do) that's normally obvious; the add-on settings panel will have options for adding login credentials.
One of the niceties of the upstream kernel is that we don't ever need to care about 1G/2G/3G RAM configurations of boards; the kernel works with whatever u-boot makes available. And yes the boot process is different (which is clearly stated in release notes and wiki, but not all users read them). The differences are in part to align with other LE platforms; but also deliberate to force clean installs and thus sidestep the carnage that comes with the Kodi Python2 > Python3 changes between legacy and current images.
I really hope to make LE work and install to internal in the future.
^ that is NOT going to happen, even if you do manage to install something: https://wiki.libreelec.tv/hardware/amlogic#install2internal
You have banned add-ons installed. No support will be offered.
Ahh, okay. Amlogic chips support multiple video output layers. The OSD (GUI) layer is 1080p max while the video layer can be 4K. The 1080p OSD limit is a silicon limitation but legacy images allow you to set 4K .. which the hardware then ignores and outputs at 1080p, while the user feels smug because they have a 4K TV and their Android box configured for 4K. It's a bit like the S905 being advertised with 2GHz CPU speed; which is 1.5`GHz if you want more than one CPU core active, but the firmware lies and reports 2GHz 
TL/DR; 1080p is the correct resolution for the GUI (hence it's the default). If you configure 4K the OSD layer is still 1080p and some TVs might stretch it, and others will render it to 1/4 of the screen. NB: We don't support 4K H264 on S905 (it works on S905X and up, but not S905) but that's prob. not an issue as 99.99999% of 4K media is HEVC. There is no HDR to SDR conversion.
H264 and HEVC are both hardware decoded. H264 playback/seeking works well. HEVC playback works wel, but seeking doesn't always work so great - the decoder is unfinished. AMLGX will not be for all users and all media, but it's easy to experiement on a spare SD card.
Please read the LE11 release notes, they explain the current state of things fairly clearly. Updates are not supported; clean install only.
Mar 30 21:44:02.661572 LibreELEC kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Mar 30 21:44:02.661646 LibreELEC kernel: usb 3-3: new high-speed USB device number 2 using xhci_hcd
Mar 30 21:44:02.661717 LibreELEC kernel: usb 2-1: new high-speed USB device number 2 using ehci-pci
Mar 30 21:44:02.661791 LibreELEC kernel: hub 1-1:1.0: USB hub found
Mar 30 21:44:02.661858 LibreELEC kernel: hub 1-1:1.0: 4 ports detected
Mar 30 21:44:02.661924 LibreELEC kernel: scsi host4: uas
Mar 30 21:44:02.662003 LibreELEC kernel: scsi 4:0:0:0: Direct-Access JMicron Disk0 0105 PQ: 0 ANSI: 6
Mar 30 21:44:02.662073 LibreELEC kernel: hub 2-1:1.0: USB hub found
Mar 30 21:44:02.662140 LibreELEC kernel: hub 2-1:1.0: 6 ports detected
Mar 30 21:44:02.662216 LibreELEC kernel: scsi 4:0:0:1: Direct-Access JMicron Disk1 0105 PQ: 0 ANSI: 6
Mar 30 21:44:02.662290 LibreELEC kernel: sd 4:0:0:0: Attached scsi generic sg0 type 0
Mar 30 21:44:02.662362 LibreELEC kernel: sd 4:0:0:1: Attached scsi generic sg1 type 0
Mar 30 21:44:02.662433 LibreELEC kernel: sd 4:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Mar 30 21:44:02.662504 LibreELEC kernel: sd 4:0:0:1: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Mar 30 21:44:02.662574 LibreELEC kernel: sd 4:0:0:0: [sda] Write Protect is off
Mar 30 21:44:02.662644 LibreELEC kernel: sd 4:0:0:0: [sda] Mode Sense: 67 00 10 08
Mar 30 21:44:02.662713 LibreELEC kernel: sd 4:0:0:1: [sdb] Write Protect is off
Mar 30 21:44:02.662784 LibreELEC kernel: sd 4:0:0:1: [sdb] Mode Sense: 67 00 10 08
Mar 30 21:44:02.662854 LibreELEC kernel: sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
Mar 30 21:44:02.662924 LibreELEC kernel: sd 4:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Mar 30 21:44:02.662998 LibreELEC kernel: sd 4:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Mar 30 21:44:02.663182 LibreELEC kernel: sd 4:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Mar 30 21:44:02.663255 LibreELEC kernel: sd 4:0:0:1: [sdb] Preferred minimum I/O size 4096 bytes
Mar 30 21:44:02.663325 LibreELEC kernel: sd 4:0:0:1: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Mar 30 21:44:02.663334 LibreELEC kernel: Alternate GPT is invalid, using primary GPT.
Mar 30 21:44:02.663341 LibreELEC kernel: sda: sda1 sda2
Mar 30 21:44:02.663409 LibreELEC kernel: sd 4:0:0:0: [sda] Attached SCSI disk
Mar 30 21:44:02.663417 LibreELEC kernel: sdb: sdb1 sdb2
Mar 30 21:44:02.663485 LibreELEC kernel: sd 4:0:0:1: [sdb] Attached SCSI disk
Mar 30 21:44:02.663556 LibreELEC kernel: usb 3-5: new full-speed USB device number 3 using xhci_hcd
Mar 30 21:44:02.664086 LibreELEC kernel: usb 3-6: new high-speed USB device number 4 using xhci_hcd
Mar 30 21:44:02.664231 LibreELEC kernel: usb-storage 3-6:1.0: USB Mass Storage device detected
Mar 30 21:44:02.664297 LibreELEC kernel: scsi host5: usb-storage 3-6:1.0
Mar 30 21:44:02.664454 LibreELEC kernel: scsi 5:0:0:0: Direct-Access SanDisk Cruzer Blade 1.26 PQ: 0 ANSI: 5
Mar 30 21:44:02.664525 LibreELEC kernel: sd 5:0:0:0: Attached scsi generic sg2 type 0
Mar 30 21:44:02.664595 LibreELEC kernel: sd 5:0:0:0: [sdc] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB)
Mar 30 21:44:02.664664 LibreELEC kernel: sd 5:0:0:0: [sdc] Write Protect is off
Mar 30 21:44:02.664735 LibreELEC kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
Mar 30 21:44:02.664805 LibreELEC kernel: sd 5:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Mar 30 21:44:02.664814 LibreELEC kernel: sdc: sdc1 sdc2
Mar 30 21:44:02.664882 LibreELEC kernel: sd 5:0:0:0: [sdc] Attached SCSI removable disk
Mar 30 21:44:02.664891 LibreELEC fsck: fsck.fat 4.2 (2021-01-31)
Mar 30 21:44:02.664900 LibreELEC fsck: /dev/sdc1: 12 files, 38232/65501 clusters
Mar 30 21:44:02.664907 LibreELEC fsck: Storage: clean, 5120/944704 files, 233249/3776128 blocks
Mar 30 21:44:02.664919 LibreELEC kernel: EXT4-fs (sdc2): mounted filesystem with ordered data mode. Quota mode: disabled.
Mar 30 21:44:04.083037 LibreELEC kernel: ntfs3: Max link count 4000
Mar 30 21:44:04.086573 LibreELEC kernel: ext3: Unknown parameter 'fmask'
Mar 30 21:44:04.086628 LibreELEC kernel: ext3: Unknown parameter 'fmask'
Mar 30 21:44:04.109703 LibreELEC kernel: ext2: Unknown parameter 'fmask'
Mar 30 21:44:04.109778 LibreELEC kernel: ext2: Unknown parameter 'fmask'
Mar 30 21:44:04.109802 LibreELEC kernel: ext4: Unknown parameter 'fmask'
Mar 30 21:44:04.109819 LibreELEC kernel: ext4: Unknown parameter 'fmask'
Mar 30 21:44:04.109839 LibreELEC kernel: squashfs: Unknown parameter 'fmask'
Mar 30 21:44:04.113106 LibreELEC kernel: squashfs: Unknown parameter 'fmask'
Mar 30 21:44:04.113141 LibreELEC kernel: F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x8e0e8966)
Mar 30 21:44:04.113157 LibreELEC kernel: F2FS-fs (sda2): Can't find valid F2FS filesystem in 1th superblock
Mar 30 21:44:04.119707 LibreELEC kernel: F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Mar 30 21:44:04.119759 LibreELEC kernel: F2FS-fs (sda2): Can't find valid F2FS filesystem in 2th superblock
Mar 30 21:44:04.119778 LibreELEC kernel: F2FS-fs (sdb2): Magic Mismatch, valid(0xf2f52010) - read(0x8e0e8966)
Mar 30 21:44:04.119793 LibreELEC kernel: F2FS-fs (sdb2): Can't find valid F2FS filesystem in 1th superblock
Mar 30 21:44:04.123273 LibreELEC kernel: F2FS-fs (sdb2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Mar 30 21:44:04.123330 LibreELEC kernel: F2FS-fs (sdb2): Can't find valid F2FS filesystem in 2th superblock
Mar 30 21:44:04.230206 LibreELEC udevil[814]: mount: mounting /dev/sdb2 on /media/4TB failed: Invalid argument
Mar 30 21:44:04.230376 LibreELEC udevil[813]: mount: mounting /dev/sda2 on /media/NewVolume failed: Invalid argument
Mar 30 21:44:04.230440 LibreELEC udevil[710]: mount: mounting /dev/sda2 on /media/NewVolume failed: No such device
Mar 30 21:44:04.230549 LibreELEC udevil[711]: mount: mounting /dev/sdb2 on /media/4TB failed: No such deviceThe update process will have absolutely zero impact. The completely different software stack that you're running post-update *can* have an impact (as we bumped ~95% of the packages in the distro; stuff has changed). The log shows both drives have issues mounting. It's unclear to me which filesystem is being used on the drives; there are messages about ext2/3/4, ntfs3 and f2fs.
As always .. no logs = no problem 
madxxcow please share a Kodi debug log when playing .. let's see what media format is used and what happens with the DRM layer.
ix.io supports 1MB or perhaps even 512K max script size (it may have been reduced). You will need to use a file sharing site of some kind.
The file.io logs show as deleted for me.
The NTP pool being set to de.pool.ntp.org suggests you've configured some things in the settings add-on. Can I ask you to take a spare SD card and do a clean install (don't set anything for NTP, etc.) then check the files again. I'd like to ensure this is a repeatable problem with the default configurations we have.
Had a typepo.
^ It seems to be a recurring issue 
I know that upgrade from 9.x to 11 wasn't supported and clean install was required but is it also the case with every future update like recently released 11.0.1? My 11.0.0 won't autoupgrade to 11.0.1?
It was undesirable to direct update from 9 > 10/11 due to the Python 2 > 3 changes in Kodi which break add-ons. There is/was no issue with updating from 10 > 11 and in the future from 10/11 > 12. At the moment auto-update requires something to be manually set on the back-end infra else the OS doesn't prompt and we (staff) frequently forget to set it giving the incorrect appearance of it being broken (the process is, but not the code). We plant to move that logic client-side in LE12 to eliminate the forgetful humans from the process. I enabled auto-update for 11.0.0 > 11.0.1 yesterday for those who didn't already bump.
