Zero/install/Boot Troubleshooting/es es - Revision history

HANLLEL at 14:21, 10 January 2022

2022-01-10T14:21:04Z

HANLLEL at 08:52, 10 January 2022

2022-01-10T08:52:21Z

HANLLEL: Created page with "{{Languages|Zero/install/Boot_Troubleshooting}} {{zero_header_es}} Radxa Zero > Instalación > zero/install/Boot_Troubleshoo..."

2022-01-10T08:30:32Z

Created page with "{{Languages|Zero/install/Boot_Troubleshooting}} {{zero_header_es}} Radxa Zero > Instalación > zero/install/Boot_Troubleshoo..."

New page

{{Languages|Zero/install/Boot_Troubleshooting}}

{{zero_header_es}}

[[zero/es_es | Radxa Zero]] > [[zero/install/es_es | Instalación]] > [[zero/install/Boot_Troubleshooting/es_es | Problemas de Inicio]]

__NOTOC__

== Una guía detallada de los problemas de inicio del Radxa Zero ==

This is a more advanced guide aiming to help user fix their boot related issues. Due to how Zero's bootloader can be stored at various locations and how each distro usually has their own quirk about how bootloader is configured, user may find it confusing why the board is not booting as they are expected. This guide will help you understand how Zero decided which bootloader to boot, the current available bootloaders from Radxa, and how to wipe and reinstall any bootloader.

Experience with Linux, [[Zero/dev/maskrom | maskrom]], and Android <code>fastboot</code> tool is highly recommended.

__TOC__

== Amlogic's boot logic ==

When you boot a bare board without any bootloader, you will see the following string printed on your serial console:

G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK:1F;SD?:0;SD:0;READ:0;CHK:1F;USB:8;

This is how the SoC finds the boot target. It will search eMMC first with 3 read instructions, each for <code>mmcblk0</code>, <code>mmcblk0boot0</code>, and <code>mmcblk0boot1</code>. If it fails to boot from eMMC it will search microSD card next, and finally the USB devices.

This means, to boot off any given storage media, you need to make sure bootloaders stored before this chain get wiped. Otherwise a different boot configuration will be used, instead of the one that came with your installation media.

Some extra messages when boot from eMMC:

# boot from mmcblk0
G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;0.0
# boot from mmcblk0boot0 after mmcblk0 is wiped
G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;0.0
# boot from mmcblk0boot1 after mmcblk0 and mmcblk0boot0 are wiped
G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;0.0

You can read more about eMMC's hardware partitions from [https://wiki.radxa.com/Zero/install/Boot_Troubleshooting#Modify_bootloader_on_eMMC here].

== Modify bootloader on eMMC ==

=== With fastboot ===

First, follow [[Zero/dev/maskrom#Enable_maskrom | maskrom guide]] to setup and load '''android-bootloader.img'''.

Once a device with ID 18d1:0d02 is shown in <code>lsusb</code> and you can see a fastboot device is detected by <code>sudo fastboot devices</code>, you can run the following command to wipe/flash bootloader image to eMMC:

# Unlock eMMC before we can do anything
sudo fastboot flashing unlock
sudo fastboot flashing unlock_critical
# Erase bootloader
sudo fastboot erase bootloader
sudo fastboot erase bootloader-boot0
sudo fastboot erase bootloader-boot1
# Flash bootloader
sudo fastboot flash bootloader bootloader.img
sudo fastboot flash bootloader-boot0 bootloader.img
sudo fastboot flash bootloader-boot1 bootloader.img

You do not need to erase before flashing, and you do not need to flash all 3 partitions.

=== From inside U-Boot ===

If your eMMC is so corrupted that any of those commands fails, you will need to erase those partitions from U-Boot console. Here is the instructions to do so as a last-ditch.

First set up [[Zero/dev/serial-console | serial console]] since U-Boot console can only be accessed via serial. Follow [[Zero/dev/maskrom#Enable_maskrom | maskrom guide]] to setup and load '''android-bootloader.img'''. After the file is loaded keep hitting Enter key in serial console until the bootloader stopped with a console waiting for command.

# mmcblk0
mmc dev 2 0
mmc erase 1 2000
# mmcblk0boot0
mmc dev 2 1
mmc erase 0 2000
# mmcblk0boot1
mmc dev 2 2
mmc erase 0 2000

Additionally if your main partition is too corrupted, that you cannot use <code>fastboot</code> to wipe those partitions, you can try the following command to wipe main partition's partition table and some extra data, making the partition non-bootable:

# WARNING!
# Potential data loss!
mmc dev 2 0
mmc erase 0 10000

Unplug and replug the power cable and now you should be able to flash bootloader according to the instruction listed in [[#From_inside_U-Boot | the previous section]].

== Modify bootloader on microSD or USB drive ==

microSD and USB drive both show in Linux system as block devices, so you can modify their bootloader in the same way. Additionally you can also use this method to flash bootloader to eMMC's main partition. However, <code>fastboot</code> has less potential to make a mistake, so it is still recommended.

First, make sure you have installed the OS of your choice to the storage media. OS installation usually comes with their own bootloader, so if you want to modify the bootloader you have to do so after the installation.

Run any of the following commands to modify bootloader on device <code>/dev/sdX</code>:

# Backup bootloader
sudo dd if=/dev/sdX of=bootloader.bak conv=fsync bs=512 skip=1 count=8192
# Erase bootloader
sudo dd if=/dev/zero of=/dev/sdX conv=fsync bs=512 seek=1 count=8192
# Flash bootloader
sudo dd if=bootloader.img of=/dev/sdX conv=fsync bs=512 seek=1 count=8192

== Common boot related issues ==

* Q: Board won't boot on my microSD/USB drive, and is booting stock Android instead.
* A: Please wipe eMMC's all 3 bootloaders and try again.

* Q: Manjaro won't boot.
* A: As of 2021-12-24, Manjaro requires the usage of vendor U-Boot, and its image does not contain any bootloader. Please flash [https://dl.radxa.com/zero/images/loader/android-bootloader.img android-bootloader.img] to your storage media.

@@ Line 61: / Line 61: @@
 === Dentro de U-Boot ===
-If your eMMC is so corrupted that any of those commands fails, you will need to erase those partitions from U-Boot console. Here is the instructions to do so as a last-ditch.
+Si tu eMMC está tan corrupta que cualquiera de esos comandos falla, necesitarás borrar esas particiones desde la consola de U-Boot. Tendrás que hacer...
-First set up [[Zero/dev/serial-console | serial console]] since U-Boot console can only be accessed via serial. Follow [[Zero/dev/maskrom#Enable_maskrom | maskrom guide]] to setup and load '''android-bootloader.img'''. After the file is loaded keep hitting Enter key in serial console until the bootloader stopped with a console waiting for command.
+Primero configuramos [[Zero/dev/serial-console | la consola serie]] ya que la consola U-Boot sólo puede ser accedida mediante serie. Sigue [[Zero/dev/maskrom#Enable_maskrom | la guía maskrom ]] para configurar y cargar '''android-bootloader.img'''. Una vez cargado el archivo, sigue pulsando la tecla Enter en la consola de serie hasta que el gestor de arranque se detenga con una consola esperando el comando.
      # mmcblk0
@@ Line 75: / Line 75: @@
      mmc erase 0 2000
-Additionally if your main partition is too corrupted, that you cannot use <code>fastboot</code> to wipe those partitions, you can try the following command to wipe main partition's partition table and some extra data, making the partition non-bootable:
+Además, si su partición principal está demasiado dañada, que no puede utilizar <code>fastboot</code> para borrar esas particiones, puedes probar el siguiente comando para borrar la tabla de particiones de la partición principal y algunos datos extra, haciendo que la partición no sea arrancable:
-     # WARNING!
+     # PELIGRO!
-     # Potential data loss!
+     # Potencial pérdida de datos!
      mmc dev 2 0
      mmc erase 0 10000
-Unplug and replug the power cable and now you should be able to flash bootloader according to the instruction listed in [[#From_inside_U-Boot | the previous section]].
+Desenchufa y vuelve a enchufar el cable de alimentación y ahora debería ser capaz de grabar el cargador de arranque de acuerdo con la instrucción que aparece en [[#From_inside_U-Boot | la sección anterior]].
-== Modify bootloader on microSD or USB drive ==
+== Modificar el cargador de arranque en la microSD o en el pendrive USB ==
-microSD and USB drive both show in Linux system as block devices, so you can modify their bootloader in the same way. Additionally you can also use this method to flash bootloader to eMMC's main partition. However, <code>fastboot</code> has less potential to make a mistake, so it is still recommended.
+La microSD y un pendrive USB se ven en el sistema Linux como dispositivos de bloques, así que puedes modificar su cargador de la misma manera. Además puedes usar también este método para grabar el cargador de arranque en la partición principal de la eMMC. Sin embargo, <code>fastboot</code> tiene menos posibilidades de cometer un error, y todavía se recomienda.
-First, make sure you have installed the OS of your choice to the storage media. OS installation usually comes with their own bootloader, so if you want to modify the bootloader you have to do so after the installation.
+Primero, asegúrate de tener instalado el Sistema Operativo de tu elección en el medio de almacenamiento. La Instalación del Sistema Operativo viene usualmente con su propio cargador de arranque, así que si quieres modificar el cargador de arranque tendrás que hacerlo después de la instalación.
-Run any of the following commands to modify bootloader on device <code>/dev/sdX</code>:
+Ejecuta los siguientes comandos para modificar el cargador de arranque en el dispositivo <code>/dev/sdX</code>:
-     # Backup bootloader
+     # Salvaguardar el cargador de arranque
      sudo dd if=/dev/sdX of=bootloader.bak conv=fsync bs=512 skip=1 count=8192
-     # Erase bootloader
+     # Borrar el cargador de arranque
      sudo dd if=/dev/zero of=/dev/sdX conv=fsync bs=512 seek=1 count=8192
-     # Flash bootloader
+     # Grabar el cargador de arranque
      sudo dd if=bootloader.img of=/dev/sdX conv=fsync bs=512 seek=1 count=8192
-== Common boot related issues ==
+== Problemas de inicio comunes ==
-* Q: Board won't boot on my microSD/USB drive, and is booting stock Android instead.
+* P: La tarjeta no inicia en la microSD/o el USB, pero inicia la imagen Android por defecto.
-* A: Please wipe eMMC's all 3 bootloaders and try again.
+* R: Por favor borra la eMMC los tres cargadores de arranque y prueba de nuevo.
-* Q: Manjaro won't boot.
+* P: Manjaro no inicia.
-* A: As of 2021-12-24, Manjaro requires the usage of vendor U-Boot, and its image does not contain any bootloader. Please flash [https://dl.radxa.com/zero/images/loader/android-bootloader.img android-bootloader.img] to your storage media.
+* R: 2021-12-24, Manjaro necesita el uso del U-Boot del vendedor, y su imagen no contiene un cargador de arranque. Por favor graba [https://dl.radxa.com/zero/images/loader/android-bootloader.img android-bootloader.img] en tu almacenamiento.

@@ Line 10: / Line 10: @@
 == Una guía detallada de los problemas de inicio del Radxa Zero ==
-This is a more advanced guide aiming to help user fix their boot related issues. Due to how Zero's bootloader can be stored at various locations and how each distro usually has their own quirk about how bootloader is configured, user may find it confusing why the board is not booting as they are expected. This guide will help you understand how Zero decided which bootloader to boot, the current available bootloaders from Radxa, and how to wipe and reinstall any bootloader.
+Esta es una guía más avanzada que ayuda a los usuarios a arreglar sus problemas de inicio. Ya que el cargador de arranque del Zero puede guardarse en varios sitios y que cada distro normalmente tiene su propio cargador de arranque con configuraciones diferentes, el usuario puede sentirse confundido al ver que la tarjeta no se inicia como esperaban. Esta guía te ayudará a comprender como el Zero selecciona el cargador de arranque a usar, los cargadores de arranque disponibles, y como eliminar y reinstalar un cargador de arranque.
-Experience with Linux, [[Zero/dev/maskrom | maskrom]], and Android <code>fastboot</code> tool is highly recommended.
+La experiencia con las herramientas, en Linux, [[Zero/dev/maskrom | maskrom]], y en Android <code>fastboot</code> será de agradecer.
 __TOC__
-== Amlogic's boot logic ==
+== Secuencia de Inicio en Procesadores Amlogic ==
-When you boot a bare board without any bootloader, you will see the following string printed on your serial console:
+Cuando inicias una tarjeta sin ningún cargador de arranque, verá la siguiente cadena de texto en la consola serie:
      G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK:1F;SD?:0;SD:0;READ:0;CHK:1F;USB:8;
-This is how the SoC finds the boot target. It will search eMMC first with 3 read instructions, each for <code>mmcblk0</code>, <code>mmcblk0boot0</code>, and <code>mmcblk0boot1</code>. If it fails to boot from eMMC it will search microSD card next, and finally the USB devices.
+Esta es la forma en la que el SoC encuentra el cargador de arranque. Primero buscará en la eMMC con 3 instrucciones de lectura, una para <code>mmcblk0</code>, otra para<code>mmcblk0boot0</code>, y para <code>mmcblk0boot1</code>. Si falla al cargar desde la eMMC buscará en la tarjeta microSD, y finalmente en los dispositivos USB.
-This means, to boot off any given storage media, you need to make sure bootloaders stored before this chain get wiped. Otherwise a different boot configuration will be used, instead of the one that came with your installation media.
+Esto significa que, para arrancar desde cualquier medio de almacenamiento, debe asegurarse de que los cargadores de arranque almacenados antes de esta cadena se borren. De lo contrario, se utilizará una configuración de arranque diferente, en lugar de la que vino con su medio de instalación.
-Some extra messages when boot from eMMC:
+Mensajes cuando se inicia desde la eMMC:
-     # boot from mmcblk0
+     # iniciar desde mmcblk0
      G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;0.0
-     # boot from mmcblk0boot0 after mmcblk0 is wiped
+     # iniciar desde mmcblk0boot0 después mmcblk0 es borrado
      G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;0.0
-     # boot from mmcblk0boot1 after mmcblk0 and mmcblk0boot0 are wiped
+     # iniciar desde mmcblk0boot1 después mmcblk0 y mmcblk0boot0 serán borrados
      G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;0.0
-You can read more about eMMC's hardware partitions from [https://wiki.radxa.com/Zero/install/Boot_Troubleshooting#Modify_bootloader_on_eMMC here].
+Puedes leer más sobre las particiones eMMC en [https://wiki.radxa.com/Zero/install/Boot_Troubleshooting#Modify_bootloader_on_eMMC esta página].
-== Modify bootloader on eMMC ==
+== Modificar el cargador de arranque en la eMMC ==
-=== With fastboot ===
+=== Con fastboot ===
-First, follow [[Zero/dev/maskrom#Enable_maskrom | maskrom guide]] to setup and load '''android-bootloader.img'''.
+Primero, sigue [[Zero/dev/maskrom#Enable_maskrom | guía maskrom ]] para configurar y cargar '''android-bootloader.img'''.
-Once a device with ID 18d1:0d02 is shown in <code>lsusb</code> and you can see a fastboot device is detected by <code>sudo fastboot devices</code>, you can run the following command to wipe/flash bootloader image to eMMC:
+Cuando el dispositivo con ID 18d1:0d02 se muestre al usar <code>lsusb</code> y puedas ver que el dispositivo fastboot es detectado por <code>sudo fastboot devices</code>, podrás ejecutar el siguiente comando para eliminar/guardar la imagen del cargador de arranque en la eMMC:
-     # Unlock eMMC before we can do anything
+     # Desbloquear la eMMC antes de todo
      sudo fastboot flashing unlock
      sudo fastboot flashing unlock_critical
-     # Erase bootloader
+     # Borrar el cargador de arranque
      sudo fastboot erase bootloader
      sudo fastboot erase bootloader-boot0
      sudo fastboot erase bootloader-boot1
-     # Flash bootloader
+     # Grabar el cargador de arranque
      sudo fastboot flash bootloader bootloader.img
      sudo fastboot flash bootloader-boot0 bootloader.img
      sudo fastboot flash bootloader-boot1 bootloader.img
-You do not need to erase before flashing, and you do not need to flash all 3 partitions.
+No necesitas borrar antes de grabar, y no necesitas grabar las 3 particiones.
-=== From inside U-Boot ===
+=== Dentro de U-Boot ===
 If your eMMC is so corrupted that any of those commands fails, you will need to erase those partitions from U-Boot console. Here is the instructions to do so as a last-ditch.