Zero/install/Boot Troubleshooting - Revision history

RadxaYuntian at 08:30, 24 April 2024

2024-04-24T08:30:09Z

Rauxon: /* Common boot related issues */

2022-11-26T21:14:33Z

‎Common boot related issues

Rauxon: /* An detailed guide for troubleshooting Radxa Zero's boot issue */

2022-11-26T20:58:23Z

‎An detailed guide for troubleshooting Radxa Zero's boot issue

RadxaYuntian at 07:43, 6 September 2022

2022-09-06T07:43:16Z

RadxaYuntian at 07:50, 30 June 2022

2022-06-30T07:50:13Z

GreetingsGQ: Adjust final item, remove circular link

2022-05-19T06:55:17Z

Adjust final item, remove circular link

GreetingsGQ: Change mmc dev from 1 to 2

2022-05-19T06:26:41Z

Change mmc dev from 1 to 2

GreetingsGQ: Correct file to load

2022-05-19T05:40:25Z

Correct file to load

RadxaYuntian at 07:07, 8 February 2022

2022-02-08T07:07:46Z

RadxaYuntian: /* TL;DR */

2022-01-17T09:28:30Z

‎TL;DR

@@ Line 33: / Line 33: @@
      # 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].

← Older revision		Revision as of 21:14, 26 November 2022
Line 146:		Line 146:
	* Q: Manjaro won't boot.		* Q: Manjaro won't boot.
	* A: Before 2022-02-04, 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. [https://forum.radxa.com/t/update-qt5-version/8552/8?u=radxayuntian Release from 2022-02-04] will contain mainline U-Boot, so the image can be flashed like other distro.		* A: Before 2022-02-04, 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. [https://forum.radxa.com/t/update-qt5-version/8552/8?u=radxayuntian Release from 2022-02-04] will contain mainline U-Boot, so the image can be flashed like other distro.
		+
		+	* Q: After using maskrom to start rz-udisk-loader.bin I cannot see the eMMC storage and see on the console (UART or HDMI): Couldn't find partition mmc 2
		+	* A: Use maskrom to load u-boot.bin and once the 'starting fastboot' message appears use 'fastboot reboot' and then use maskrom to push rz-udisk-loader.bin

@@ Line 7: / Line 7: @@
 __NOTOC__
-== An detailed guide for troubleshooting Radxa Zero's boot issue ==
+== A detailed guide for troubleshooting Radxa Zero's boot issue ==
 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.

← Older revision		Revision as of 07:43, 6 September 2022
Line 74:		Line 74:

	You do not need to erase before flashing, and you do not need to flash all 3 partitions. Beware '''sudo fastboot flash mmc0''' could potentially damage your existing data.		You do not need to erase before flashing, and you do not need to flash all 3 partitions. Beware '''sudo fastboot flash mmc0''' could potentially damage your existing data.
		+
		+	=== With Android fastboot ===
		+
		+	In some cases, you will have to use Android's bootloader. This is based on Amlogic's U-Boot source code, so it will behave differently from upstream U-Boot.
		+
		+	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 image to eMMC:
		+
		+	# Unlock eMMC before we can do anything
		+	sudo fastboot unlock
		+	sudo fastboot unlock_critical
		+	# Backup bootloader
		+	sudo fastboot fetch bootloader bootloader.bak
		+	sudo fastboot fetch bootloader-boot0 bootloader-boot0.bak
		+	sudo fastboot fetch bootloader-boot1 bootloader-boot1.bak
		+	# 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. Beware '''sudo fastboot flash bootloader''' could potentially damage your existing data.

	=== From inside U-Boot ===		=== From inside U-Boot ===

@@ Line 40: / Line 40: @@
 === TL;DR ===
-We have updated our [[Zero/install/eMMC_erase | eMMC erase]] guide, which does the following operations automatically and should fix most boot related issues.
+We have updated our [[Zero/install/eMMC_erase | eMMC erase]] guide, which does the below operations automatically, and should fix most boot related issues.
 Beware this will result in data loss since the partition header will be wiped as well. If you need to preserve the data, either make a disk image before wiping, or follow the manual guide below.
 === With fastboot ===
-First, follow [[Zero/dev/maskrom#Enable_maskrom | maskrom guide]] to setup and load '''android-bootloader.img'''.
+First, follow [[Zero/dev/maskrom#Enable_maskrom | maskrom guide]] to setup and load '''rz-fastboot-loader.bin'''.
-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:
+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 image to eMMC:
-     # Unlock eMMC before we can do anything
+     # Erase eMMC
-    sudo fastboot flashing unlock
+     sudo fastboot erase mmc0
-    sudo fastboot flashing unlock_critical
+     sudo fastboot erase mmc0boot0
-    # Erase bootloader
+     sudo fastboot erase mmc0boot1
-     sudo fastboot erase bootloader
+     # Flash eMMC
-     sudo fastboot erase bootloader-boot0
+     sudo fastboot flash mmc0 linux_distro.img
-     sudo fastboot erase bootloader-boot1
+     sudo fastboot flash mmc0boot0 bootloader.img
-     # Flash bootloader
+     sudo fastboot flash mmc0boot1 bootloader.img
-     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.
+You do not need to erase before flashing, and you do not need to flash all 3 partitions. Beware '''sudo fastboot flash mmc0''' could potentially damage your existing data.
 === 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.
+If your eMMC is so corrupt that above 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 '''u-boot.bin'''. After the file is loaded keep hitting Enter key in serial console until the bootloader stopped with a console waiting for command.
+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 '''u-boot.bin'''. After the file is loaded keep hitting Ctrl+C in serial console until the bootloader stopped with a console waiting for command.
      # mmcblk0
      mmc dev 2 0
-     mmc erase 0 2000
+     mmc erase 0 20000
      # mmcblk0boot0
      mmc dev 2 1
@@ Line 79: / Line 92: @@
      mmc dev 2 2
      mmc erase 0 2000
 Restart and you should be able to flash the bootloader according to the instructions listed in the [[Zero/install/eMMC_erase | eMMC erase]] guide.

@@ Line 87: / Line 87: @@
      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]].
+Restart and you should be able to flash the bootloader according to the instructions listed in the [[Zero/install/eMMC_erase | eMMC erase]] guide.
 == Modify bootloader on microSD or USB drive ==

← Older revision		Revision as of 07:07, 8 February 2022
Line 110:		Line 110:

	* Q: Manjaro won't boot.		* 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.	+	* A: Before 2022-02-04, 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. [https://forum.radxa.com/t/update-qt5-version/8552/8?u=radxayuntian Release from 2022-02-04] will contain mainline U-Boot, so the image can be flashed like other distro.