My Kiii is working with this device tree (gxbb_p200_2G_1Gbit.dtb) , but I haven't wifi 5GHz, only 2,4GHz (in Android, there is 5Ghz wifi). Do you have the same problem?
It works for me. Have you changed the name of gxbb_p200_2G_1Gbit.dtb file?
Wysłane z mojego Apollo przy użyciu Tapatalka
I have had 2 TX5Pro S905X boxes Sh#t themselves in the last 2 weeks and upon opening them the first thing i noticed is what Crap Circuit Boards are used with these new chips. Seriously bad sandwich boards with a Murky Resin Finish.
I am done with these S905X Chips Boxes and now know why they are cheaper than the s905 Chip Boxes.Sorry had to get that out.
Question is , is this KIII Sorted for you ?
Yeap!
I have already installed 8.0.0b on my KIII and successfully updated to 8.0.0c via Update folder. Everything works, confirmed. I have even wireless connection and bluetooth working thanks to correct device tree (gxbb_p200_2G_1Gbit.dtb).
KIII is ok for libreELEC, at least in my case.
Wysłane z mojego Apollo przy użyciu Tapatalka
Hi kszaq,
Thanks for the advice, I will do the procedure starting first with your recommended built & I will share my results.
I have checked the LIBREelec 7.0.3.12i with the device tree gxbb_p200_2G_1Gbit.dtb installed on a clean SD card for testing (as per kszaq's suggestion) in my KIII device. I am confirming as follows:
1. That device tree is correct & works with KIII. I got even my wifi connection back (currently I have LIBREelec 7.0.2.005 installed and have no wifi probably due to wrong device tree - I am connected with Lan cable). Bluetooth status is "Disconnected" and cannot do anything about. Looks like it doesn't work, but I am not using it anyway, so not a big deal for me.
2. LIBREelec 7.0.3.12i works without problems. I have all spdif passtrough voice including DTS-HD & Dolby True HD to my receiver without any distortions. 
What I noticed is, that this version of LIBREElec is not localized - I prefer to have it in my mother language (like 7.0.2.005), but this is not really bothering me. One thing though, which I have overlooked in the description - it is based on Kodi Jarvis 16.1 version, so same which I have now. I wanted to have the kodi Krypton 17.0, therefore I am going to test now on my KIII the LIBRelec 8.0.0b based on this version. I will also burn it on clean SD card just in case. If everything works fine I will carry out the Update procedure following the kszaq's instruction in the other topic.
kszaq
Great job btw & thanks for the advice!
[hr]You can first try running one of the newer builds from a separate SD card. There you can change dtb.img as many times as you want without making any change to your device or risking a brick. I would recommend trying gxbb_p200_2G_1Gbit.dtb.
Hi kszaq,
Thanks for the advice, I will do the procedure starting first with your recommended built & I will share my results.
Hi dear kszaq,First of all thanks for your efforts. I'm running your LibreElec 7.0.2.005 build on my KIII S905 device, and I'm happy with it. But I would love to update it to one of your newer releases. Unfortunately, none of the releases after 005 build does work on my device. It just doesnt boot, it just doesnt go past the Amlogic S905 boot logo. I've tried every device tree out there, but none seem to work. When I revert back to 005 build, it works like normal. I'm using an external sd-card to boot LibreElec.
I think none of the newer DTB.img are compatible with my device. It's a KIII bought from AliExpress but I think there are different models of this KIII device. It has 2gb ram and 16gb internal memory with 1gbit ethernet. I've attached the stock rom dtb.img . Hope you (or someone else) can help me out with a working dtb.img so I can keep using and updating your firmwares. Thanks a lot in advance!
Hi Merziyas,
I was just about to update my KIII device with Krypton LIBREelec (7.0.3.012i), so I was reading to find a correct tree for my device. It looks like I have exactly same configuration as you (LIBREelec 7.0.2.005 on SD card for KIII device) and based on your experience I have stopped my approach. Have you found or received from somebody the correct working tree for our device? If so, do you mind to share it?
Thanks in advance.
