I was asked to update a friends older Libreelec running on an SD card on their Beelink GT 1 clone 2Gb/16Gb/1GB Lan(which runs GT1 Android perfectly).
But I ran into some issues.
Firstly in the initial post of this thread there is mention of a new activation of the universal multi-boot but no mention of what, where and how this part is achieved.
So I soldiered on with the knowledge that I had from previous installation.
Flashed the latest S912 image (LibreELEC-AMLGX.arm-9.80-devel-20190821140333-07b919f-s912.img)
It was to clear which DTB should be used but as this was a q201 board (which the previous Libreelec version had a DTB for this setup) it seemed logical to start with the meson-gxm-q201.dtb, so I modified uEnv.ini and extlinux.conf as appropriate.
Popped in the SD card and started up the box, which initially booted to Android, so I installed the Reboot to Libreelec app, ran it and it proceeded to boot from the SD card and I saw the Libreelec logo.
But after waiting a little while, I noticed that a reboot had been automatically initiated, where it would go through the same process again and again, in some form of boot loop. It did this a number of times before just stopping with no activity and a blank screen.
So I switched the box off and put the SD card into my PC to see what it;s state was. It seemed to be at the same state that it was in before placing it onto the Android box.
I wondered whether the dtb was incompatible, so after a little searching it seemed that the extlinux.conf or meson-gxm-rbox-pro might potentially be compatible but after trying each, the same boot loop activity occurred.
So I am stuck as to what direction to go in next and wonder whether this mysterious universal multi-boot thing holds the answer?