Posts by cigarron

Quote from buzzmarshall

Ya thats cool...

Still tho, even when loading CE or AE on a sd or stick to enable that those original installs on the box altered the existing factory bootloader ONCE to allow the device on reboot to now check for a bootable OS someplace other then just the internal flash... from the factory normally a box just boots up into Android but does have the ability to load outside sources which is how the Android recovery works...

To enable a off box bootable source tho there is a script in most builds that will alter the internal bootloaders setup to check elsewhere... essentially your telling the manufacturers u-boot to check other places then just internal memory and then saving those new settings into u-boots storage area so it can be used from that point forward anytime the device reboots. So even tho your still running CE or AE on external media they at one point in their original 1st boot made those alterations to u-boot on the device...

Once that intially happens normally you never need worry bout that anymore and just need to worry bout things like the proper dtb file for the device with its matching build...

With that in mind what i am getting at is that the method CE/AE and LE go about making the alteration to u-boots startup environment is no longer the SAME...

For along time seeing as historically CE/AE and others started life as Forks of LE that once any One of them were initially setup to run internally or externally the could all take advantage of U-boots altered environment...

As CE/AE now insist they aren't really LE forks anymore their way is Not supported by Balbes (LE) builds anymore as his scripts work slightly differently... tho i quess if one wanted to spend enough time analyzing the differences a common method could be done...

Personally even tho i have followed along for years and built all of the Distro's going back to and predating even OpenELEC which kinda started all of these types of frame works. I have a tool i created years ago that i use to create boot loaders for all of my projects on pretty much any Arm based device as i develop on ST and TI as well as the typical Amlogic or Rockchip SoC's that use Arm cores... I do RE work so i do a lot of messing around with proprietary Devices and SoC's but essentially they function in similar manners at the core...

Display More

Thank you very much for the reply.

You can explain to me then how is the process that you say Balbes:

"you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems."

What is "the USB Burn Tool"? Do I have to flash the Android? If so, it is too much for me to lose everything I have mounted in the box with Android. Is there another recovery method for boot boot?

Sorry for my ignorance.

Best regards.

Quote from buzzmarshall

En lo que respecta al archivo dtb ... es un estándar, por lo que editarlos y adaptarlos si comprende esos archivos no es tan difícil, pero creo que podría perderse algo más ...

En cuanto al arranque, es la forma en que las diferentes horquillas de LE escriben en el firmware original (cargador de arranque) para permitirle verificar y arrancar desde medios alternativos y luego el flash interno ...

Inicialmente, durante un tiempo, la mayoría de los Distro usaron los mismos scripts para editar el cargador de arranque del fabricante para permitir el mecanismo de carga alternativo, pero ese ya no es el caso, que es lo que creo que Balbes estaba tratando de señalarle, y eso para que funcione con su Las compilaciones de LE y Armbian que necesita restaurar al estado de fábrica y luego usar su método más nuevo para crear sus ediciones del cargador de arranque permitiendo que LE y Armbian se carguen correctamente ...

Todavía necesitará el dtb correcto, pero para que sus compilaciones funcionen, debe hacer que el dispositivo arranque de una manera compatible con sus compilaciones, que es lo que creo que tiene problemas con ...

Alguien me corrija si estoy equivocado aunque ...

Espero que despeje parte del agua fangosa ...

Display More

If you mean original firmware, the box has not been modified, continue with the factory Android. I do not try to boot from the internal flash, but from an external SD with the "stick" method. I don't know if I explain myself. I do not have CORE / ALEX in the internal flash, I have always started in dual, always respecting the original ANDROID.

I guess LE also starts in dual mode, doesn't it?

I already assumed that it was not a problem of how to record the SD card.

Which leads me to think that it is a problem with the structure of the DBT file that I am trying to use.

The question then is: is the DBT file that I have uploaded adaptable to LIBREELEC ?. If so, can anyone adapt it for LE?

All this without forgetting that the purpose is for the SAT / DTT to work with the adapter that I indicated

Thank you.

(p.d. Where can I find this meson-gxbb-ki- plus .dtb for example?)

Quote from balbes150

Read carefully the first post of this topic.

Does that mean I have to use LibreELEC.USB-SD.Creator.Win32 to prepare the SD card?

it is not worth recording the image with the linux disc recorder (dd)

Good morning,

I have an Ariva 4K combo box (SAT + DTT) with which I have tested both COREELEC and ALEXELEC with a DBT image (attached file), and I get it to boot without problems.

The tests I want to do with LIBREELEC is for SAT and DTT tuners. They are AVL6762 and AVL6211 (AV2026) controllers. In COREELEC and ALEXELEC I can't scan anything with TVHEADEND.

If with the image I use for CORE and ALEX I can boot from the SD. Why with LIBREELEC from the SD card does not start ?. I have changed uEnv.ini to indicate my image. Should the image be dts or dbt ?. If it has to be dts, could someone change it for me?

Can somebody help me.

Thank you very much.