Identify the present and intended releases
Record the installed LibreELEC version, Kodi version and hardware model. Then identify the intended supported release from the official download route. The wiki’s numbered examples illustrate file types and workflows; do not mistake an old example version for the current release you should install.
Make a short list of essential authorised add-ons and sources. A system update can leave the operating system running while an important add-on needs its own compatible release. Verify that dependency before choosing a migration date, especially when the box is the household’s only working player.
Choose the documented update route
LibreELEC describes its settings add-on and other update methods, with different roles for update archives and installation images. Follow the current instructions matching the exact hardware and release. Creating fresh installation media is a different operation from updating a working system.
Preserve the existing configuration and record how to recover it before proceeding. Keep the backup away from the target storage. Avoid using a copied shell command containing a historical board name or release number merely because it appeared in a wiki example.
Check the complete viewing task afterward
After a supported update, verify navigation, one permitted local sample and the essential authorised source separately. Record failures by stage. A successful boot does not prove that every add-on, guide mapping and audio output has survived unchanged.
Keep the previous configuration and release information until the new setup is understood. If support is needed, report hardware, old and new releases, update method and the exact changed behaviour. This reference helps make the migration reviewable; it does not run an update, promise rollback compatibility or claim a test of every LibreELEC image.