Older cards may indeed solve boot issues. A 2GB card seems to have helped my case. Not at first, but that may be due to factors in this particular box.
About installing to the internal memory, I know it's discouraged from and deprecated, but would help me, at my risk; no queries in case of failure. Is the solution in finding and running the script?
1) A DTB that forces 50MHz. How do I find it?
2) The boot medium. One successful install was from a 2GB SD with no markings at to its class. It's in use, but if you think it can help, I'll try it. This time I had an 8GB SD HC class 4. LE failed to boot from it, so I used a 4GB TS4GJFV30 USB stick. Other systems did boot from SD but with the same results as from USB.
3) I reach Kodi only at initial configuration, when you need to hit Next to proceed, and it doesn't seem to complete. Can I exit that and enable debugging? As the boot now ends only in failed services, how can I reach a state of the first boot and Kodi again? In Android Recovery? Flash the Android image?
Thanks again!
Sadly, no. Sorry for troubling you. The storage seems faulty. The installation starts as usual with partition resizing, etc. A reboot brings mount errors, need to exit, more errors (Kernel panic). Kodi may appear, but setting it up ends in (a need to do) a reboot. The final series of errors is failed services and dependencies. There may also appear a request to do a repair, but to no avail.
I have tried several systems, new and old, with similar results. Alas, the attempts have ruined a working AE installation, seemingly irrevocably. Flashing the Android image doesn't produce a working system anymore, previously not perfect but possible. I'll ask elsewhere if there can be images to flash in Android Recovery, it works.
Thanks for your help!
Further to booting on a box with S905X, I've tried all DTBs for it, with much the same result, and noticed one error that may make sense: could not mount UUID=59a29572-99d0-44c6-b35a-98d279afa82a (the one in uEnv.ini).
If this is a place for issues with installation, my boot attempts cause dozens of errors when booting from USB: services fail to start etc. KODI appeared once but not for long. It won't boot from SD at all, but maybe the card was to blame. A log would help, but as far as I know, you need a network to connect via SSH, and apparently boot attempts damaged the existing OS in the internal. I can take pictures.
Box: OzoneHD (S905X ARM Coretex-A53; ARM Mali-450)
Previous OS: AlexELEC-S9XX.arm-3.1.8 (Android behaved badly and somehow I chose AE; it ran fine, but KODI had a few issues)
Attempted latest LE: http://chewitt.libreelec.tv/testing/LibreE…arm-10.95.0-box
DTB:
AE gxl_p212_2g_nand
LE dtb_name=/dtb/meson-gxl-s905x-p212.dtb
1) If the device tree is wrong, LE won't boot at all?
2) Why can AE fail to boot from internal now? Booting from SD/USB is not supposed to affect it. There was a request to do a repair, but I ignored it in hopes of a successful boot, and it never came on again.
3) Out of curiosity, AE builds are called piracy, does it mean they contain stolen code and are not an independent, proprietary product, so to speak?
Not sure if this relates to the OS or Kodi (then a query for kodi.tv). Issues with playback, seeking and subtitles. AlexELEC with Kodi 18.5 for mostly HD H264 off an SD. Playing a first file is always or mostly fine. Any next file may play or always plays shifted, so I need to stop and start.
1) Reason enough to try a new build?
2) I have read in http://wiki.libreelec.tv/hardware/amlogic.
Still, a few questions. It appears I need builds marked as 'box'. Is my only source http://test.libreelec.tv/11.0/Amlogic/box?
Should I consider test builds in other locations?
Builds for 10 are not for Amlogic (http://test.libreelec.tv/10.0/Generic), so unsuitable?
