You wasn't very clear in your initial post, please wait for the next release as there will be a switch to the LE kernel which may solve your issue, it will require you using the 9.0 dtb then.
Sorry for beeing not clear enough.
Is there any plan for next release? Days? Weeks? Months? Just to have a rough idea.
You need to use 8.2 dtb
I have used 8.2, see link!
Does not solve the issue. Testen with gxbb_p200_1G_mxq_pro_4k.dtb (which matches the one I used with 8.0)
kszaq Thanks for having a look at the issue.
Also for comparison, log from 8.0 with working DTB
serial_console_log_working_dtb.txt
Maybe kszaq has an idea what's wrong with the dtb?
I managed to attach the serial console with an FTDI and captured the output of boot process where the screen get's stuck at mxqpro logo.
Hope that helps for further analysis?!
serial_console_log_broken_dtb.txt
---- update
Tried to check the output, but did not find anything special, problematical, except maybe a lot of messages like
"recover_current_block_mapping invalid page data!!"
But boot process continues after that.
The 9.0 ones only work with the LE/amlogic kernel which I do not use, you must use the ones from the 8.2 folder for these builds, it does state that in the README on the downloads.
DTB's are very specific to the kernel in use and they must match for your device to boot.
Okay, that's now clear to me.
But... at least one 1G option (my box only has 1G) from 8.2 folder should work, right? What should I do if none is working? Even the one you attached a few post earlier?
Is this really a "guesswork only" task? Isn't there an option to "see" whats going wrong? No log, no output, no trace?
-- update
with help of How to Extract a Device Tree File from Android Firmware Files, I decompiled the 8.0.1 working device tree, and compared it 8.2 device tree with same file-naming-scheme. There are a lot of differences, but as I absolutely have no device-tree-skills, I have no idea if this is correct, or if something has to be changed.
See attached, decompiled device tree sources.
working 8.0
gxbb_p200_1G_mxq_pro_4k.dtd_8.0.txt
matching 8.2, but not working
Maybe you need to use another dtb.
Sure, but which? I tried all of them (the 1G option, except wetek):
Index of /s905/8.2/device_trees/S905
I also tried all p200 1G options from here:
Index of /s905/9.0/device_trees
All I can say: This DTB works with 8.0.1: gxbb_p200_1G_mxq_pro_4k.dtb
But with LE9.0 alpha I had no luck yet.
I'm running out of ideas. Isn't there anyone using MXQ Pro 4k out there?
I didn't extract it from any version, it's direct from the source, please don't get confused I only asked you to do that because I didn't have access to a computer to send you the file yesterday.
Downloaded your dtb, copied it to libreelec partition, named it dtb.img ... tried to boot... still stuck at mxqpro logo 
You have just stated the obvious. You need to mount the newer version to get the file, I already told you this, I would upload it but I have no access to a computer, the DTBs are all different on major Kodi versions due to changes in the kernel if you do not use the correct DTB it will not boot!
Sorry, it was not clear to me that i have to mount the newer version. And it still makes somehow no sense to me:
If I try to run the newer version (the version I'm trying to install/update?), and it does not work: why should I try to extract the DTB from it?
I guess you referenced a "working new version", but I don't have one. --> still confused a bit.
alex0801 try the following DTB
Thanks, I will try this.
But to understand it completely: From which version did you extract this?
Which one? My SD-card i just prepared? Please be more precise where i can "pull out the latest version".
If I boot my backedup old version, I can of course access /usr/share/bootloader. But then I can only access the old dtb, which will not match the new kernel and whatnot of new LE 9.0 alpha version.
I already tried using this dtb, but issue is still there GDPR-2 ...
No idea where I can get a version that works...
Anyone out there using an MXQPro4k with LE9.0 alpha with success?
Then yes it's most probably the dtb at fault, you can try and mount your external card/drive and browse to /usr/share/bootloader to pull out the latest version, I would upload it for you but I'm away from a machine right now.
Which one? My SD-card i just prepared? Please be more precise where i can "pull out the latest version".
if you can't get past the mxq logo then this would most probably be a dtb issue, can you still boot to android?
Rebooting to android still works, yes.
I have a MXQ Pro 4k box with S905 (1GB RAM, 8GB flash).
Currently it is running kszaq's 8.0.1k version with "gxbb_p200_1G_mxq_pro_4k.dtb". Runs fine.
But I want to update to be able to use Amazon VOD Plugin:
I downloaded LibreELEC-S905.arm-8.90.2.img.gz
as well as the device-tree gxbb_p200_1G_mxq_pro_4k.dtb
I put the image onto SD with help of LE USB creator. I copied the dtp file as "dtb.img" to libreelec-partition. Unmount SD card, put into box, powered up and ... Boot stucks at MXQPRO logo ... forever.
I tried also device-tree from 9.0 folder: gxbb_p200_1G_mxq_pro_4k.dtb
Same issue. Thank god I created a dd-image from my previos, working version.
Any suggestion how to overcome this boot-issue? Is there anything I can do to find out what's going wrong?
The only thing that I see from the video: The first image of the new channel is coming up faster (which gives better user experience --> faster system). But time "switch channel <-> channel is playing well and continuously" is still 3-4sec.
I'll try RB LE this weekend...
Regarding the "improved channel changing speed": If I count the seconds from the moment the UI tells me the channel is about to change until the new channel is playing well, it's about 3-4sec in your video. Sorry, but where's the improvement? I have right now the same speed.
Weos and libreelec are little bit different systems . Latest dvb driver is different
Of course they are. One is Android LInux, one is KODI JeOS.
But according to RB LE build script, RB LE is using (=downloading) the latest binary blob from Wetek. So the binary driver should be exactly the same, or?
Nevertheless, I bought a 2nd mirosd card and will test latest "stable" RB LE (rb-krypton4) and test a bit.
I'm also thinking of buying a separate sat-ip-server (have some more TVs in the house to upgrade from old-school sat SetTopBoxes...). But this has currently no priority.
zbigzbig20
Any comment on my last post?
@anyone else
Am I the only one facing this issue?
