To boot the system for the first time you have to use one of the following:
- toothpick method: disconnect the power supply, insert card/drive, push reset button and connect the power while holding the button. Wait until LibreELEC logo appears and release the button
Or put a dummy.zip file on your SD/USB and from the Update App in Android, select it as the source and click Update. 
I have installed (to nand) LE on several X96 amlogic s905x boxes, gave em to friends, but 3 of those friends have 4K TV's and are saying the Kodi menu (under LE) is too large.
Do you mean the Kodi homepage? They probably need to run Video calibration to reduce overscan on their TVs.
Also, a bit off topic I know but, how do you find the remote controls of the X96 boxes, what range are they functional at? Do the remote IR receivers work? (I asked as I have some of these boxes and would like to know if issues I have are common to them all 
)
. . . running LibreELEC from internal memory . . .
So SD card / USB install wouldn't work for you?
. . . if you select the autoupdate source LE7, the menu "System" disappears itself. . .
I'm pretty sure there's no Update Channel for these builds, so nothing is missed by leaving that section on it's defaults
it does. this is the relevant part . . .
needs to be inside <advancedsettings> and <video> tags of course
Very useful, thanks
[hr]
Not really sure why you edited my quote or why it would work for me just because it works for you. . . .
It's a feature that is supposed to work for all. I shortened the quote of your post in my response to only the relevant parts, so as not to create an outrageously long thread.
Those reading the response, can click the little green arrow in the quote to be taken to, and read your full, untouched post if they haven't already read it (those that have, really don't need the complete post presented to them again)
Glad that you discovered you no longer need any workaround in autostart.sh 
It looks to me like Kodi is started before the network is ready. . . even with "wait for network" enabled. . .I use this workaround to halt Kodi for one ping to Google (or max 10 seconds):
The wait for network option in LE settings works fine here, wonder why you have to 're-invent the wheel' ? :s
A good example is LibeELEC generic advancedsettings file (which is not used for Amlogic projects!):
Thanks kszaq, Still works with Amlogic though, I presume ?
[hr]
great work looks like the freeze on reboot issue is resolved by disabling the temp sensor.
more like worked around, I think
[hr]
But wouldn't this driver be needed to do proper thermal management?
Seems likely eh?
Where did that quote come from ?
And if it's always out of sync by the same time you can specify the audio offset in advancedsettings.xml as well. I've always had to do this (195 ms for 24p and 70 ms for other refresh rates in my case, I think it depends on your screen and the time it needs for video processing).
an example, perhaps ? . . .
7.1 audio it's always out of sync...
You can adjust the sync from the fullscreen OSD
can you flash stock 011 minix u1 firmware and then install 012 with temp enabled?Based on the changelog its fixes the boot issue, which means it should boot with temp build
Official Release - NEO U1 FW011 - 20161201 | MINIX Forum - Official
I tried this, along with dozens of other P200 / P200_2G ROMs, over the last day or so and, so far have not found a suitable replacement for the MiniMX-G. Most failed to even boot to USB and, those that did froze within 5 reboots.
The Tronsmart Vega S95 Telos FW had me going for a while, with an impressive 15 consecutive reboots, but then froze on the 16th.
The led status was reversed with this ROM, so it probably would have been a bit weird having the light glowing when the box was off anyhow 
Seems that the only way to move on to these 32bit builds is to use the disabled temp sensor variant 
[hr]
@kszaq
Is the Boot issue only present in the 7.0.x builds or are the 7.9.0 alpha builds also affected ?
EDIT:
nvm just found out it affects both 
Beelink is now challenging Nexbox as the number #1 contender for Stay Away Product.
Not now that the boot freeze issue is fixable (sadly not the case yet with the S905's I have)
What's wrong with Nexbox? My A95X (S905X) boxes work perfectly
Unconnected reset button, is amongst the list. Until the 'dummy.zip' trick was discovered, making things like setting up LE on external media real difficult (and, of course, if you installed LE to internal, made life difficult to go back to Android).
Also, broken U-BOOT causes issues waking from suspend for devs like Kzsaq
Maybe you got lucky
The disabled sensor version is working fine on the non Beelink MiniMX-G.
Only issue I've noticed is it seems to be generate random MAC addresses.
Thanks for your hard work, as always
Poida If you don't need CPU temperature readings, I will release two 7.0.3.012 variants: with and without it. In that case with and without freezes.
I don't actually care if I can see the temp or not. So your releases are all welcome.
I'm only searching for Android FW that is not affected by this issue because I suspect that there are temp related safeguards built-in and am concerned that disabling the sensor might also disable these.
More for the benefit of others who can't afford to take the chance 
OTA updates from 103L1 did persuade the MiniMX-G to boot LE from USB but all versions up to current froze within 6 reboots
Also tried custom build suggested by someone but that resulted in a black screen.
So far, haven't found any FW for this device that is not in the 10xL1 range.
The search for suitable Android FW for MiniMX-G continues . . .
The non Beelink MiniMX-G scene, in contrast, no so simple. So far 104L1, 105L1, 106L1 refuse to even boot from SD
103L1 got stuck on reboot 4 
