BeeLink GT King - CoreELEC-Amlogic-ng.arm-9.1-nightly - Generic

Just installed nightly build CoreELEC-Amlogic-ng.arm-9.1-nightly_20190722-Generic.img.gz.
During boot I get the message:
Your devicetree is out of date.
Please update it to resume normal startup.
Normal startup in 60s…

Question 1: how to update the devicetree (in 60 seconds)?
Question 2: why countdown for 60 seconds as CoreElec will boot anyway with the outdated devicetree?

Thanks for all the great work the CoreElec Team is doing.


p.s. Feel free to move this post to another category if this one is not appropriate.

Updating the device tree is a copy and paste job on your computer, follow the exact same steps that you did when you first installed CoreELEC ie copy from device_trees folder and rename.

The countdown is there to make users aware that they need to update the device tree.

OK. I did create a SD with the nightly build CoreELEC-Amlogic-ng.arm-9.1-nightly_20190722-Generic.img.gz and moved the BeeLink GT King devicetree to the root directory of the SD and renamed it to dtb.img conform the installation instructions for CoreElec.I then inserted the SD in the BeeLink device. As expected, CoreElec started a clean install on the SD. However, all I wanted was the upgrade of my CoreElec installation running on an USBstick to the 20190722 nightly build. When I follow the normal update instructions by copying this nightly build to the .update directory I get the message:
Your devicetree is out of date.
Please update it to resume normal startup.
Normal startup in 60s…

The solution is to somehow copy the SD image to the .update folder of CoreElec. But how to do that under Win10? Please give me some guidance.

TIA, Baderks

Plug your USB drive into the PC, and replace the DTB.


Thank you. That did the trick. I’m a bit embarrassed that I did not think of that myself.
Maybe it would be wise to amend CoreElec’s How to update CoreElec with this instruction to update the devicetree.
What I do not know is whether or not the update of the devicetree is needed every time you update CoreElec. If that is the case, it would break the automatic update of CoreElec.


No, you don’t need to update the dtb in the future, it is automatic.

Hey there,
I’m having trouble getting the remote to turn off the box. I’ve the remote.conf file suggested above and that solved the problem of not being able to turn on the box with the remote after turning it off.
But how can i make it turn off or suspend with the remote power button? Any CLI command to get the keycode sent with i press the button to check what’s being sent?


The vendor bootloader does not support wake up. I am currently working on a small tool to fix the wake up errors. I guess in the next 2-3 weeks… There will be than a how-to guide on this forum.

After placing this boot2k3 remote.conf file in /storage/.config/ I was able to use the remote to switch on/off my BeeLink GT King box.

I’ve placed that file in storage/.config and now I’m able to turn on after shutdown/sleep but when in kodi if I press the power button nothing happens. I would like it to show the power menu or shutdown/put the box to sleep.
My remote doesn’t have the air mouse function… Could this be the issue? Maybe a different id?
Thanks for your help.

My remote is without mouse as well. So that is not the point.
You can use ir-keytable (available on CoreElec) to see what keys are picked up by the BeeLink GT King and what code is generated. Lots of info on ir-keytable available on the internet.
I do not know with what action you can replace the power action in the remote.conf show the power menu. Changing this action could also break the power on part of the power action.

Success with your endeavour.

Hello friends, the Orbsmart S86 works too with this image.

Great to hear, which DTB are you using with it?

I use “g12b_s922x_beelink_gt_king.dtb”

1 Like

By using remote.conf posted early I can power on the box, but not power off. I managed this file to get it power on and off by using the original remote.

#amlogic NEC remote
factory_code = 0x7F800001
work_mode = 0
repeat_enable = 1
repeat_delay = 120
repeat_peroid = 33
release_delay = 121
debug_enable = 1

0x59 116
0x51 116