diff --git a/_pages/ar_SA/seedminer.txt b/_pages/ar_SA/seedminer.txt
index c99db98353..333617c42a 100644
--- a/_pages/ar_SA/seedminer.txt
+++ b/_pages/ar_SA/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/ar_SA/troubleshooting.txt b/_pages/ar_SA/troubleshooting.txt
index 8a55c8ed04..33f0dd86f2 100644
--- a/_pages/ar_SA/troubleshooting.txt
+++ b/_pages/ar_SA/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/bg_BG/seedminer.txt b/_pages/bg_BG/seedminer.txt
index c99db98353..333617c42a 100644
--- a/_pages/bg_BG/seedminer.txt
+++ b/_pages/bg_BG/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/bg_BG/troubleshooting.txt b/_pages/bg_BG/troubleshooting.txt
index 8a55c8ed04..33f0dd86f2 100644
--- a/_pages/bg_BG/troubleshooting.txt
+++ b/_pages/bg_BG/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/ca_ES/seedminer.txt b/_pages/ca_ES/seedminer.txt
index c99db98353..333617c42a 100644
--- a/_pages/ca_ES/seedminer.txt
+++ b/_pages/ca_ES/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/ca_ES/troubleshooting.txt b/_pages/ca_ES/troubleshooting.txt
index 8a55c8ed04..33f0dd86f2 100644
--- a/_pages/ca_ES/troubleshooting.txt
+++ b/_pages/ca_ES/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/cs_CZ/seedminer.txt b/_pages/cs_CZ/seedminer.txt
index c99db98353..333617c42a 100644
--- a/_pages/cs_CZ/seedminer.txt
+++ b/_pages/cs_CZ/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/cs_CZ/troubleshooting.txt b/_pages/cs_CZ/troubleshooting.txt
index 8a55c8ed04..33f0dd86f2 100644
--- a/_pages/cs_CZ/troubleshooting.txt
+++ b/_pages/cs_CZ/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/de_DE/seedminer.txt b/_pages/de_DE/seedminer.txt
index 4edbdd6b61..657a58bed8 100644
--- a/_pages/de_DE/seedminer.txt
+++ b/_pages/de_DE/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/de_DE/troubleshooting.txt b/_pages/de_DE/troubleshooting.txt
index 4bd11087a5..0f79d2098e 100644
--- a/_pages/de_DE/troubleshooting.txt
+++ b/_pages/de_DE/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/el_GR/seedminer.txt b/_pages/el_GR/seedminer.txt
index 05b67290a2..f27426ea87 100644
--- a/_pages/el_GR/seedminer.txt
+++ b/_pages/el_GR/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/el_GR/troubleshooting.txt b/_pages/el_GR/troubleshooting.txt
index ffbec9bf0e..7c1a35a6de 100644
--- a/_pages/el_GR/troubleshooting.txt
+++ b/_pages/el_GR/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/en_PT/seedminer.txt b/_pages/en_PT/seedminer.txt
index a3003c9f46..4bd642e695 100644
--- a/_pages/en_PT/seedminer.txt
+++ b/_pages/en_PT/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/en_PT/troubleshooting.txt b/_pages/en_PT/troubleshooting.txt
index 49384147b4..9abe74ae99 100644
--- a/_pages/en_PT/troubleshooting.txt
+++ b/_pages/en_PT/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/es_ES/seedminer.txt b/_pages/es_ES/seedminer.txt
index f859b52021..658f96ed2b 100644
--- a/_pages/es_ES/seedminer.txt
+++ b/_pages/es_ES/seedminer.txt
@@ -21,6 +21,7 @@ Este método utiliza una tarjeta gráfica potente para realizar los cálculos ne
 1. Copia el nombre de 32 caracteres de la carpeta que hay dentro de Nintendo 3DS
   + No abras más carpetas dentro de ésta
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/es_ES/troubleshooting.txt b/_pages/es_ES/troubleshooting.txt
index e6cdb0f766..9c3a5cba01 100644
--- a/_pages/es_ES/troubleshooting.txt
+++ b/_pages/es_ES/troubleshooting.txt
@@ -253,9 +253,17 @@ Tu consola tuvo custom firmware en el pasado, por lo que no se te pidió hacer a
 Los pasos detallados a continuación asumen que tu consola tiene un setup moderno de custom firmware (boot9strap + Luma3DS 8.0 o superior). Si tu consola tiene una configuración antigua (por ejemplo, algo basado en arm9loaderhax o menuhax), deberías actualizar dicha configuración antes de seguir estas instrucciones.
 {: .notice--info}
 
-### La consola se queda con pantalla en negro y la luz azul se apaga
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-Hay un problema con el archivo `boot.firm` (falta, está mal colocado o está corrupto). Descarga la [última versión de Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) y coloca `boot.firm` en la raíz de tu tarjeta SD, reemplazando cualquier archivo existente. Asegúrate de extraer el archivo ZIP con cualquier herramienta que no sea WinRAR, ya que se sabe que causa problemas con los archivos relacionados con 3DS.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 Si escuchas un "pop", potencialmente acompañado de la luz de la pantalla parpadeando un segundo, hay un problema en el hardware de tu consola (cable de luz de fondo desconectado, por ejemplo). Es posible que tu consola encienda sosteniéndola en distintas orientaciones.
 
diff --git a/_pages/fi_FI/seedminer.txt b/_pages/fi_FI/seedminer.txt
index 9efd99bfe4..05b25a7b04 100644
--- a/_pages/fi_FI/seedminer.txt
+++ b/_pages/fi_FI/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/fi_FI/troubleshooting.txt b/_pages/fi_FI/troubleshooting.txt
index 130438d215..cd9e0b3a97 100644
--- a/_pages/fi_FI/troubleshooting.txt
+++ b/_pages/fi_FI/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/fr_FR/seedminer.txt b/_pages/fr_FR/seedminer.txt
index 3a1bf148f7..a3f16ebf4e 100644
--- a/_pages/fr_FR/seedminer.txt
+++ b/_pages/fr_FR/seedminer.txt
@@ -21,6 +21,7 @@ Cette méthode utilise une carte graphique puissante pour effectuer les calculs
 1. Copiez le nom du dossier qui fait 32 caractères de long que vous voyez dans Nintendo 3DS
   + N'allez plus dans aucun dossier
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/fr_FR/troubleshooting.txt b/_pages/fr_FR/troubleshooting.txt
index d53c1d13d5..a98fe6245e 100644
--- a/_pages/fr_FR/troubleshooting.txt
+++ b/_pages/fr_FR/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/he_IL/seedminer.txt b/_pages/he_IL/seedminer.txt
index 7c985de7bf..667664f728 100644
--- a/_pages/he_IL/seedminer.txt
+++ b/_pages/he_IL/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/he_IL/troubleshooting.txt b/_pages/he_IL/troubleshooting.txt
index 3fd885b5f8..a3231a0e4c 100644
--- a/_pages/he_IL/troubleshooting.txt
+++ b/_pages/he_IL/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/hr_HR/seedminer.txt b/_pages/hr_HR/seedminer.txt
index c99db98353..333617c42a 100644
--- a/_pages/hr_HR/seedminer.txt
+++ b/_pages/hr_HR/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/hr_HR/troubleshooting.txt b/_pages/hr_HR/troubleshooting.txt
index 8a55c8ed04..33f0dd86f2 100644
--- a/_pages/hr_HR/troubleshooting.txt
+++ b/_pages/hr_HR/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/hu_HU/seedminer.txt b/_pages/hu_HU/seedminer.txt
index 8ee2d5d165..19d019bd7e 100644
--- a/_pages/hu_HU/seedminer.txt
+++ b/_pages/hu_HU/seedminer.txt
@@ -21,6 +21,7 @@ Ez a módszer egy erős grafikus kártyát használ a szükséges számítások
 1. Másold le a 32 karakter hosszú nevét annak a mappának, amit látsz
   + Nem menj beljebb több mappát
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/hu_HU/troubleshooting.txt b/_pages/hu_HU/troubleshooting.txt
index 26968aadb6..71277c8eb2 100644
--- a/_pages/hu_HU/troubleshooting.txt
+++ b/_pages/hu_HU/troubleshooting.txt
@@ -253,9 +253,17 @@ Az eszközödnek volt egyedi firmware-je a múltban, így nem lett automatikusan
 Az itt leírt lépések általában feltételezik, hogy az eszközöd modern egyedi firmware telepítéssel rendelkezik (boot9strap + Luma3DS 8.0 vagy nagyobb). Ha a konzolod régebbi homebrew telepítés (például valami ami arm9loaderhax vagy menuhax alapú), frissítened kell a telepítésed, mielőtt kipróbálod ezeket a lépéseket.
 {: .notice--info}
 
-### Az eszközöm fekete képernyőn ragad, és a kék fény kikapcsol
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-Probléma van a `boot.firm` fájloddal (nem jó, hiányzik, rossz helyen van vagy sérült). Töltsd le a legutolsó kiadását az [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest)-nek és rakd a `boot.firm` fájlt az SD kártyád gyökerébe, felülírva bármilyen létező fájlt. Legyél biztos abban, hogy a ZIP fájlt más eszközzel csomagolod ki, mint a WinRAR, mert ismert, hogy problémái vannak a 3DS-sel kapcsolatos fájlokkal.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 Ha hallod a "pattanó hangot", ami potenciálisan a háttérvilágítás bekapcsolását kíséri a másodperc egy részéig, akkor hardver problémád van az eszközöddel (mint például lecsatlakozott háttérvilágítás kábel). Lehetséges, hogy be tudod kapcsolni és az eszközödet megfelelő szögben tartva.
 
diff --git a/_pages/id_ID/seedminer.txt b/_pages/id_ID/seedminer.txt
index c99db98353..333617c42a 100644
--- a/_pages/id_ID/seedminer.txt
+++ b/_pages/id_ID/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/id_ID/troubleshooting.txt b/_pages/id_ID/troubleshooting.txt
index 8a55c8ed04..33f0dd86f2 100644
--- a/_pages/id_ID/troubleshooting.txt
+++ b/_pages/id_ID/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/it_IT/seedminer.txt b/_pages/it_IT/seedminer.txt
index 27686a24f0..d2c738a67e 100644
--- a/_pages/it_IT/seedminer.txt
+++ b/_pages/it_IT/seedminer.txt
@@ -21,6 +21,7 @@ Questo metodo utilizza una scheda grafica di fascia alta per eseguire i calcoli
 1. Copia la stringa di 32 caratteri del nome della cartella presente dentro il Nintendo 3DS
   + Non entrare in ulteriori cartelle
   + Se vedi più cartelle di 32 caratteri, segui [queste istruzioni](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/it_IT/troubleshooting.txt b/_pages/it_IT/troubleshooting.txt
index 78bb017309..4187fcd346 100644
--- a/_pages/it_IT/troubleshooting.txt
+++ b/_pages/it_IT/troubleshooting.txt
@@ -253,9 +253,17 @@ La tua console ha avuto un custom firmware in passato, quindi non ti è stato au
 I passaggi qui dettagliati generalmente presuppongono che la tua console abbia un'installazione moderna del custom firmware (boot9strap + Luma3DS 8.0 o superiore). Se la tua console sta eseguendo una vecchia configurazione (ad esempio, qualcosa basato su arm9loaderhax o menuhax), dovresti aggiornare la tua installazione prima di seguire queste istruzioni.
 {: .notice--info}
 
-### La mia console si blocca su una schermata nera e la luce blu si spegne
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-C'è un problema con il tuo file `boot.firm` (è mancante, mal posizionato o corrotto). Scarica [l'ultima versione di Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) e posiziona il file `boot.firm` nella directory principale della tua scheda SD, sostituendo qualunque file preesistente. Assicurati di non stare estraendo il file ZIP con WinRAR, in quanto è noto per causare problemi con file relativi al 3DS.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 Se si sente un "suono scoppiettante", potenzialmente seguito dalla retroilluminazione accendersi per un istante, c'è un problema hardware con la tua console (come un cavo della retroilluminazione disconnesso). Potresti riuscire ad accendere la console tenendola in determinate posizioni.
 
diff --git a/_pages/ja_JP/seedminer.txt b/_pages/ja_JP/seedminer.txt
index e61b42f5d9..44014c5339 100644
--- a/_pages/ja_JP/seedminer.txt
+++ b/_pages/ja_JP/seedminer.txt
@@ -21,6 +21,7 @@ For information on how Seedminer works, see [this presentation](https://zoogie.g
 1. 表示されている32文字のフォルダ名をコピーします。
   + まだそれ以上フォルダを展開しないでください
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/ja_JP/troubleshooting.txt b/_pages/ja_JP/troubleshooting.txt
index 999daa99a1..59317fbc10 100644
--- a/_pages/ja_JP/troubleshooting.txt
+++ b/_pages/ja_JP/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/ko_KR/a9lh-to-b9s.txt b/_pages/ko_KR/a9lh-to-b9s.txt
index 227c67b219..c321ae9909 100644
--- a/_pages/ko_KR/a9lh-to-b9s.txt
+++ b/_pages/ko_KR/a9lh-to-b9s.txt
@@ -11,7 +11,8 @@ title: A9LH를 B9S로 업데이트
 
 이제부터 모든 Luma3DS의 릴리스는 boot9strap과 sighax에만 대응하는 `.firm`형식으로 업데이트 됩니다. 그것은 곧 Luma3DS를 업데이트 하려면, 이 페이지를 통해 업데이트를 해야 한다는 것과 같습니다,
 
-To use the [magnet](https://wikipedia.org/wiki/Magnet_URI_scheme) links on this page, you will need a torrent client like [qBittorrent](https://www.qbittorrent.org/download.php) or [Deluge](http://dev.deluge-torrent.org/wiki/Download).
+이 페이지의 [마그넷](https://wikipedia.org/wiki/Magnet_URI_scheme)링크를 사용하려면
+ [qBittorrent](https://www.qbittorrent.org/download.php) 또는 [Deluge](http://dev.deluge-torrent.org/wiki/Download)와 같은 토렌트 클라이언트가 필요합니다.
 
 이 페이지에 있는 `.7z` 파일을 압축 해제하기 위해서는, [7-Zip](http://www.7-zip.org/) 또는 [The Unarchiver](https://theunarchiver.com/) 같은 압축 해제 프로그램이 필요합니다.
 
@@ -30,7 +31,7 @@ To use the [magnet](https://wikipedia.org/wiki/Magnet_URI_scheme) links on this
 * 최신 버전의 [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) 
 * v7.0.5 버전의 [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/tag/v7.0.5) *(`.7z` 파일)*
 * 최신 버전의 [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/latest)
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip) 
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip) 
 ### 진행 방법
 
 #### 섹션 I - 준비 작업
diff --git a/_pages/ko_KR/ctrtransfer.txt b/_pages/ko_KR/ctrtransfer.txt
index 4e5e0775ea..5c8e466750 100644
--- a/_pages/ko_KR/ctrtransfer.txt
+++ b/_pages/ko_KR/ctrtransfer.txt
@@ -18,7 +18,8 @@ title: "CTRTransfer"
 
 ### 준비물
 
-To use the [magnet](https://wikipedia.org/wiki/Magnet_URI_scheme) links on this page, you will need a torrent client like [qBittorrent](https://www.qbittorrent.org/download.php) or [Deluge](http://dev.deluge-torrent.org/wiki/Download).
+이 페이지의 [마그넷](https://wikipedia.org/wiki/Magnet_URI_scheme)링크를 사용하려면
+ [qBittorrent](https://www.qbittorrent.org/download.php) 또는 [Deluge](http://dev.deluge-torrent.org/wiki/Download)와 같은 토렌트 클라이언트가 필요합니다.
 {: .notice--warning}
 
 * 최신 버전의 [GodMode9](https://github.com/d0k3/GodMode9/releases/latest)
diff --git a/_pages/ko_KR/f3-(linux).txt b/_pages/ko_KR/f3-(linux).txt
index 1ddc0292c8..f738342fd4 100644
--- a/_pages/ko_KR/f3-(linux).txt
+++ b/_pages/ko_KR/f3-(linux).txt
@@ -10,7 +10,7 @@ title: "F3 (Linux)"
 
 SD 카드의 용량과 컴퓨터의 속도에 따라 최대 몇 시간이 걸릴 수 있습니다!
 
-이 페이지는 Linux 사용자를 위한 페이지입니다. If you are not on Linux, check out the [H2testw (Windows)](h2testw-(windows)) or [F3XSwift (Mac)](f3xswift-(mac)) pages.
+이 페이지는 Linux 사용자를 위한 페이지입니다. Linux 사용자가 아니라면 [H2testw (windows)](h2testw-(windows)) 또는 [F3XSwift (Mac)](f3xswift-(mac)) 페이지를 참고해 주세요.
 
 ### 준비물
 
diff --git a/_pages/ko_KR/flashing-ntrboot-(3ds-multi-system).txt b/_pages/ko_KR/flashing-ntrboot-(3ds-multi-system).txt
index 27cb4052c0..c277a0748a 100644
--- a/_pages/ko_KR/flashing-ntrboot-(3ds-multi-system).txt
+++ b/_pages/ko_KR/flashing-ntrboot-(3ds-multi-system).txt
@@ -19,7 +19,7 @@ title: "ntrboot 플래싱 (3DS 두 대)"
 * 두 개의 3DS 기기 
   + **소스 3DS**: 이미 boot9strap을 구동하고 있는 3DS
   + **타겟 3DS** CFW를 설치할 3DS
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4-ntr.zip)
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4-ntr.zip)
 * 최신 버전의 [ntrboot_flasher](https://github.com/ntrteam/ntrboot_flasher/releases/latest)
 
 ### 진행 방법
diff --git a/_pages/ko_KR/flashing-ntrboot-(3ds-single-system).txt b/_pages/ko_KR/flashing-ntrboot-(3ds-single-system).txt
index 97b7228e3a..4d1211cec3 100644
--- a/_pages/ko_KR/flashing-ntrboot-(3ds-single-system).txt
+++ b/_pages/ko_KR/flashing-ntrboot-(3ds-single-system).txt
@@ -16,7 +16,7 @@ title: "ntrboot 플래싱 (단일 3DS)"
 ### 준비물
 
 * ntrboot를 설치할 수 있는 플래시카트
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4-ntr.zip)
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4-ntr.zip)
 * 최신 버전의 [ntrboot_flasher_nds](https://github.com/jason0597/ntrboot_flasher_nds/releases/latest)
 
 ### 진행 방법
diff --git a/_pages/ko_KR/flashing-ntrboot-(nds).txt b/_pages/ko_KR/flashing-ntrboot-(nds).txt
index 26b838f340..1c694f2dc2 100644
--- a/_pages/ko_KR/flashing-ntrboot-(nds).txt
+++ b/_pages/ko_KR/flashing-ntrboot-(nds).txt
@@ -19,7 +19,7 @@ title: "ntrboot 플래싱 (NDS)"
 * 두 기기 
   + **소스 NDS/NDSL**: 플래시카트와 호환되는 닌텐도 DS 또는 DS Lite
   + **타겟 3DS** CFW를 설치할 3DS
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4-ntr.zip) 
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4-ntr.zip) 
 * 최신 버전의 [ntrboot_flasher_nds](https://github.com/jason0597/ntrboot_flasher_nds/releases/latest)
 
 ### 진행 방법
diff --git a/_pages/ko_KR/homebrew-launcher-(soundhax).txt b/_pages/ko_KR/homebrew-launcher-(soundhax).txt
index 27124dedef..5679b6aea9 100644
--- a/_pages/ko_KR/homebrew-launcher-(soundhax).txt
+++ b/_pages/ko_KR/homebrew-launcher-(soundhax).txt
@@ -17,7 +17,7 @@ udsploit(다음 페이지에 사용) 이 작동하기 위해서 무선통신이
 * 최신 버전의 [Soundhax](http://soundhax.com) *(기기의 지역과 버전에 맞게 선택)*
   + 만약 Soundhax가 브라우저에서 실행 불가능한 비디오로 나오면, Ctrl+S 또는 Cmd+S를 눌러 컴퓨터로 저장해 주세요.
 * 최신 버전의 [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/latest)
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
 * 최신 버전의 [safehax](https://github.com/TiniVi/safehax/releases/latest) *(`.3dsx` 파일)*
 * 최신 버전의 [udsploit](https://github.com/smealum/udsploit/releases/latest)
 *최신 버전의 [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest)
diff --git a/_pages/ko_KR/installing-boot9strap-(hardmod).txt b/_pages/ko_KR/installing-boot9strap-(hardmod).txt
index f9506aedc5..df18dec38a 100644
--- a/_pages/ko_KR/installing-boot9strap-(hardmod).txt
+++ b/_pages/ko_KR/installing-boot9strap-(hardmod).txt
@@ -10,7 +10,8 @@ title: "boot9strap 설치 (하드모드)"
 
 하드모드 다운그레이드는 현재 [이곳](https://www.3dbrew.org/wiki/3DS_System_Flaws)에 자세히 설명되어 있는 "FIRM partitions known-plaintext" 익스플로잇을 구현한 것입니다.
 
-To use the [magnet](https://wikipedia.org/wiki/Magnet_URI_scheme) links on this page, you will need a torrent client like [qBittorrent](https://www.qbittorrent.org/download.php) or [Deluge](http://dev.deluge-torrent.org/wiki/Download).
+이 페이지의 [마그넷](https://wikipedia.org/wiki/Magnet_URI_scheme)링크를 사용하려면
+ [qBittorrent](https://www.qbittorrent.org/download.php) 또는 [Deluge](http://dev.deluge-torrent.org/wiki/Download)와 같은 토렌트 클라이언트가 필요합니다.
 
 이 페이지에 있는 `.7z` 파일을 압축 해제하기 위해서는, [7-Zip](http://www.7-zip.org/) 또는 [The Unarchiver](https://theunarchiver.com/) 같은 압축 해제 프로그램이 필요합니다.
 
@@ -19,7 +20,7 @@ To use the [magnet](https://wikipedia.org/wiki/Magnet_URI_scheme) links on this
 ### 준비물
 
 * [하드모드](https://gbatemp.net/threads/414498/)를 이용하여 추출한 보유 기기의 NAND 이미지
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
 * 최신 버전의 [hardmod-b9s-installer](https://github.com/ihaveamac/hardmod-b9s-installer/releases/latest)
   + Mac과 Linux 사용자는 '.py'를 구동하기 위해 [Python 3](https://www.python.org/downloads/)이 설치되어 있어야 하는 반면에 Windows 사용자들은 컴파일된 '.exe'파일을 사용할 수 있습니다
 *최신 버전의 [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) 
diff --git a/_pages/ko_KR/installing-boot9strap-(kartdlphax).txt b/_pages/ko_KR/installing-boot9strap-(kartdlphax).txt
index 5728ab2ddf..8f0ad650a9 100644
--- a/_pages/ko_KR/installing-boot9strap-(kartdlphax).txt
+++ b/_pages/ko_KR/installing-boot9strap-(kartdlphax).txt
@@ -24,7 +24,7 @@ kartdlphax는 마리오 카트 7의 다운로드 플레이 모드를 사용하
 **타겟 3DS** (커스텀 펌웨어를 설치하려고 하는 3DS)에서:
 
 * 최신 버전의 [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/latest)
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
 * 최신 버전의 [일반 Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest)
 
 #### Section I - Prep Work (source 3DS)
diff --git a/_pages/ko_KR/installing-boot9strap-(ntrboot).txt b/_pages/ko_KR/installing-boot9strap-(ntrboot).txt
index 01c7888d94..d2854f782f 100644
--- a/_pages/ko_KR/installing-boot9strap-(ntrboot).txt
+++ b/_pages/ko_KR/installing-boot9strap-(ntrboot).txt
@@ -6,14 +6,15 @@ title: "boot9strap 설치 (ntrboot)"
 
 ### 중요
 
-To use the [magnet](https://wikipedia.org/wiki/Magnet_URI_scheme) links on this page, you will need a torrent client like [qBittorrent](https://www.qbittorrent.org/download.php) or [Deluge](http://dev.deluge-torrent.org/wiki/Download).
+이 페이지의 [마그넷](https://wikipedia.org/wiki/Magnet_URI_scheme)링크를 사용하려면
+ [qBittorrent](https://www.qbittorrent.org/download.php) 또는 [Deluge](http://dev.deluge-torrent.org/wiki/Download)와 같은 토렌트 클라이언트가 필요합니다.
 
 ### 준비물
 
 당신의 기기의 슬립모드를 작동시킬 자석 (접는 형식의 기기를 사용할 경우만)
 * ntrboot 플래시된 플래시카트
 * 최신 버전의 [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/latest)
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
 *최신 버전의 [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) 
 
 ### 진행 방법
diff --git a/_pages/ko_KR/installing-boot9strap-(pichaxx).txt b/_pages/ko_KR/installing-boot9strap-(pichaxx).txt
index 68530a6966..7d4613223c 100644
--- a/_pages/ko_KR/installing-boot9strap-(pichaxx).txt
+++ b/_pages/ko_KR/installing-boot9strap-(pichaxx).txt
@@ -18,7 +18,7 @@ title: "boot9strap 설치 (PicHaxx)"
   + 포켓몬 피크로스를 설치하려면 SD 카드가 들어가 있어야 합니다
 * [Seedminer](seedminer)에서 받은 `movable.sed` 파일
 * 최신 버전의 [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/latest)
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
 * 최신 버전의 [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest)
 * 최신 버전의 [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest)
 
diff --git a/_pages/ko_KR/installing-boot9strap-(soundhax).txt b/_pages/ko_KR/installing-boot9strap-(soundhax).txt
index 7a4d027884..7c4060b02e 100644
--- a/_pages/ko_KR/installing-boot9strap-(soundhax).txt
+++ b/_pages/ko_KR/installing-boot9strap-(soundhax).txt
@@ -13,7 +13,7 @@ Soundhax는 (universal-otherapp과 사용할 때) 모든 지역의 1.0.0 이상
 * 최신 버전의 [Soundhax](http://soundhax.com) *(기기의 지역과 버전에 맞게 선택)*
   + 만약 Soundhax가 브라우저에서 실행 불가능한 비디오로 나오면, Ctrl+S 또는 Cmd+S를 눌러 컴퓨터로 저장해 주세요.
 * 최신 버전의 [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/latest)
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
 * 최신 버전의 [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest)
 * 최신 버전의 [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest)
 
diff --git a/_pages/ko_KR/installing-boot9strap-(usm).txt b/_pages/ko_KR/installing-boot9strap-(usm).txt
index fa746ff506..ca1ef7bdc7 100644
--- a/_pages/ko_KR/installing-boot9strap-(usm).txt
+++ b/_pages/ko_KR/installing-boot9strap-(usm).txt
@@ -23,7 +23,7 @@ SAFE_MODE 펌웨어를 해킹하기 위해, 익스플로잇이 되어있는 Wi-F
 
 * [Seedminer](seedminer)에서 받은 `movable.sed` 파일
 * 최신 버전의 [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/latest)
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
 *최신 버전의 [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest)
 
 
@@ -79,7 +79,7 @@ SAFE_MODE 펌웨어를 해킹하기 위해, 익스플로잇이 되어있는 Wi-F
   + [이 (영어) 사진](https://uwuu.ca/images/safemode_highlighted.png)처럼 하시면 됩니다
 1. 익스플로잇이 성공적이었다면 SafeB9SInstaller로 부팅되었을 것입니다
 
-#### Section IV - Installing boot9strap
+#### 섹션 IV - boot9strap 설치
 
 1. 메시지가 나타나면, boot9strap을 설치하기 위하여 화면에 주어진 키 조합을 입력해 주세요
   + If the top screen is blank, power off your device and re-do Section III
diff --git a/_pages/ko_KR/region-changing.txt b/_pages/ko_KR/region-changing.txt
index 48bd4ec6d0..36898b16fa 100644
--- a/_pages/ko_KR/region-changing.txt
+++ b/_pages/ko_KR/region-changing.txt
@@ -31,7 +31,8 @@ Luma3DS가 지역 외 게임들과 [타이틀별 지역 에뮬레이션](https:/
 
 ### 준비물
 
-To use the [magnet](https://wikipedia.org/wiki/Magnet_URI_scheme) links on this page, you will need a torrent client like [qBittorrent](https://www.qbittorrent.org/download.php) or [Deluge](http://dev.deluge-torrent.org/wiki/Download).
+이 페이지의 [마그넷](https://wikipedia.org/wiki/Magnet_URI_scheme)링크를 사용하려면
+ [qBittorrent](https://www.qbittorrent.org/download.php) 또는 [Deluge](http://dev.deluge-torrent.org/wiki/Download)와 같은 토렌트 클라이언트가 필요합니다.
 {: .notice--warning}
 
 * 최신 버전의 [GodMode9](https://github.com/d0k3/GodMode9/releases/latest)
diff --git a/_pages/ko_KR/seedminer.txt b/_pages/ko_KR/seedminer.txt
index 68c0bef9ef..3e7cc48423 100644
--- a/_pages/ko_KR/seedminer.txt
+++ b/_pages/ko_KR/seedminer.txt
@@ -20,7 +20,8 @@ Seedminer이 정확히 어떻게 작동하는지 더 배우고싶다면 [이 프
 1. SD 카드의 `Nintendo 3DS` 폴더를 열어 주세요
 1. `Nintendo 3DS` 폴더 내 32글자의 폴더 이름을 복사해 주세요
   + 다른 폴더 안에 들어가지 마세요
-  + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + 만약 32-자리 폴더가 여러 개 보인다면 [이 설명서](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder) 를 따르세요.
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/ko_KR/troubleshooting.txt b/_pages/ko_KR/troubleshooting.txt
index 59da0c775b..6de92d381e 100644
--- a/_pages/ko_KR/troubleshooting.txt
+++ b/_pages/ko_KR/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/ko_KR/updating-b9s.txt b/_pages/ko_KR/updating-b9s.txt
index a941634118..f091cd444f 100644
--- a/_pages/ko_KR/updating-b9s.txt
+++ b/_pages/ko_KR/updating-b9s.txt
@@ -14,7 +14,7 @@ title: "B9S 업데이트"
 ### 준비물
 
 * 최신 버전의 [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/latest)
-* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
+* 최신 버전의 [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip)
 * 최신 버전의 [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest)
 
 ### 진행 방법
diff --git a/_pages/ms_MY/seedminer.txt b/_pages/ms_MY/seedminer.txt
index cc9279c67d..6805bd443f 100644
--- a/_pages/ms_MY/seedminer.txt
+++ b/_pages/ms_MY/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/ms_MY/troubleshooting.txt b/_pages/ms_MY/troubleshooting.txt
index 9a4c920532..97878b2e85 100644
--- a/_pages/ms_MY/troubleshooting.txt
+++ b/_pages/ms_MY/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/nl_NL/seedminer.txt b/_pages/nl_NL/seedminer.txt
index 8f8284028a..73cbe52ac9 100644
--- a/_pages/nl_NL/seedminer.txt
+++ b/_pages/nl_NL/seedminer.txt
@@ -21,6 +21,7 @@ Deze methode gebruikt een krachtige grafische kaart om de benodigde berekeningen
 1. Kopieer de 32-tekens lange naam van de map die je ziet in de Nintendo 3DS map
   + Ga niet binnen in andere mappen
   + Als je meerdere mappen ziet met 32-tekens lange namen, volg dan [deze instructies](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-map)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/nl_NL/troubleshooting.txt b/_pages/nl_NL/troubleshooting.txt
index 3715b77685..f59456a8c2 100644
--- a/_pages/nl_NL/troubleshooting.txt
+++ b/_pages/nl_NL/troubleshooting.txt
@@ -253,9 +253,17 @@ Je console had al custom firmware in het verleden, dus werd je niet automatisch
 De instructies die hier vermeld worden gaan er van uit dat je console een moderne custom firmware setup heeft (boot9strap + Luma3DS 8.0 of hoger). Als je console een oudere homebrew setup heeft (bijvoorbeeld iets gebaseerd op arm9loaderhax of menuhax), dan moet je updaten voor je deze instructies probeert.
 {: .notice--info}
 
-### Mijn apparaat zit vast op een zwart scherm en het blauwe licht gaat uit
+### Mijn apparaat schakelt uit wanneer ik het probeer aan te zetten, of de notificatie LED toont een kleur bij het opstarten
 
-Er is een probleem met je `boot.firm` bestand (het ontbreekt, werd misplaatst of is corrupted). Download de nieuwste versie van [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) en plaats `boot.firm` op de hoofdmap van je SD-kaart, ter vervanging van het bestaande bestand. Zorg ervoor dat je het ZIP-bestand uitpakt met een andere tool dan WinRAR, omdat het bekend is dat het problemen veroorzaakt met 3DS-gerelateerde bestanden.
+Er is een probleem met je `boot.firm` bestand. Als je [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4) gebruikt, kan je 3DS notificatie LED een bepaalde kleur flashen. Deze kleur wordt gebruikt om problemen met je `boot.firm` bestand op SD-kaart of intern geheugen te diagnosticeren. Bij oudere versies van boot9strap zal het blauwe licht bijna onmiddellijk uitgeschakeld worden wanneer je je apparaat probeert op te starten.
+
+Als de notificatie LED knippert:
+
+-**Wit**: Je 3DS was niet in staat om `boot.firm` te vinden op je SD-kaart of in je interne geheugen.
+-**Magenta**: Je 3DS was niet in staat om `boot.firm` te vinden op je SD-kaart. Het kon `boot.firm` vinden in het interne geheugen, maar het bestand is beschadigd.
+-**Red**: Je 3DS kon `boot.firm` vinden op je SD-kaart en in je interne geheugen, maar beide bestanden zijn beschadigd.
+
+Je kunt een nieuw `boot.firm` bestand krijgen door de [nieuwste versie van Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) te downloaden, het uitpakken en `boot.firm` plaatsen op de hoofdmap van je SD-kaart. Indien je `boot.firm` bestand consequent gedetecteerd wordt als beschadigd, controleer je best je SD-kaart op fouten ([Windows](h2testw-(windows)), [Linux](f3-(linux)), of [macOS](f3xswift-(mac))). Houd er ook rekening mee dat de 3DS problemen heeft met bestanden die zijn uitgepakt met WinRAR.
 
 Als je een "pop" hoort, mogelijks samen met de achtergrondverlichting die eventjes aanschiet, is er een hardware probleem met je console (zoals een achtergrondlicht kabel die niet aangesloten is). Je zou je apparaat kunnen laten opstarten door het op bepaalde hoeken vast te houden.
 
diff --git a/_pages/no_NO/seedminer.txt b/_pages/no_NO/seedminer.txt
index 8ce5c55a02..c96547bc4f 100644
--- a/_pages/no_NO/seedminer.txt
+++ b/_pages/no_NO/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/no_NO/troubleshooting.txt b/_pages/no_NO/troubleshooting.txt
index 6e926a2a91..704cd3daab 100644
--- a/_pages/no_NO/troubleshooting.txt
+++ b/_pages/no_NO/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/pl_PL/seedminer.txt b/_pages/pl_PL/seedminer.txt
index 4514f1de64..50fd4b4eef 100644
--- a/_pages/pl_PL/seedminer.txt
+++ b/_pages/pl_PL/seedminer.txt
@@ -21,6 +21,7 @@ Metoda ta wymaga użycia wydajnej karty graficznej, aby wykonać potrzebne oblic
 1. Skopiuj 32 znakową nazwę folderu który widzisz w folderze Nintendo 3DS
   + Nie wchodź w żadne inne foldery
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/pl_PL/troubleshooting.txt b/_pages/pl_PL/troubleshooting.txt
index 932ff7dc5f..d6e9fd10ac 100644
--- a/_pages/pl_PL/troubleshooting.txt
+++ b/_pages/pl_PL/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/pt_BR/seedminer.txt b/_pages/pt_BR/seedminer.txt
index 8a2b0e1651..bafc4f1037 100644
--- a/_pages/pt_BR/seedminer.txt
+++ b/_pages/pt_BR/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/pt_BR/troubleshooting.txt b/_pages/pt_BR/troubleshooting.txt
index db3bd60f62..92d6475da6 100644
--- a/_pages/pt_BR/troubleshooting.txt
+++ b/_pages/pt_BR/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/pt_PT/seedminer.txt b/_pages/pt_PT/seedminer.txt
index e463d722db..93ae5837f2 100644
--- a/_pages/pt_PT/seedminer.txt
+++ b/_pages/pt_PT/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/pt_PT/troubleshooting.txt b/_pages/pt_PT/troubleshooting.txt
index 8a55c8ed04..33f0dd86f2 100644
--- a/_pages/pt_PT/troubleshooting.txt
+++ b/_pages/pt_PT/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/ro_RO/seedminer.txt b/_pages/ro_RO/seedminer.txt
index 804b990b59..2b8e7d4409 100644
--- a/_pages/ro_RO/seedminer.txt
+++ b/_pages/ro_RO/seedminer.txt
@@ -21,6 +21,7 @@ Această metodă folosește o placă video puternică pentru a realiza calculele
 1. Copiați numele lung de 32 de caractere al folderului care îl vedeți în Nintendo 3DS
   + Nu accesați în alte foldere
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/ro_RO/troubleshooting.txt b/_pages/ro_RO/troubleshooting.txt
index 258d5841b3..c29e7c4864 100644
--- a/_pages/ro_RO/troubleshooting.txt
+++ b/_pages/ro_RO/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/ru_RU/seedminer.txt b/_pages/ru_RU/seedminer.txt
index fc2d9eca28..b5812e95b8 100644
--- a/_pages/ru_RU/seedminer.txt
+++ b/_pages/ru_RU/seedminer.txt
@@ -21,6 +21,7 @@ For information on how Seedminer works, see [this presentation](https://zoogie.g
 1. Скопируйте имя папки из 32 символов, которую вы видите внутри папки Nintendo 3DS
   + Не заходите дальше внутрь других папок
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/ru_RU/troubleshooting.txt b/_pages/ru_RU/troubleshooting.txt
index d4e0cc5f16..6a8949087e 100644
--- a/_pages/ru_RU/troubleshooting.txt
+++ b/_pages/ru_RU/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/sv_SE/seedminer.txt b/_pages/sv_SE/seedminer.txt
index c99db98353..333617c42a 100644
--- a/_pages/sv_SE/seedminer.txt
+++ b/_pages/sv_SE/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/sv_SE/troubleshooting.txt b/_pages/sv_SE/troubleshooting.txt
index b94ed96301..dabe889129 100644
--- a/_pages/sv_SE/troubleshooting.txt
+++ b/_pages/sv_SE/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/th_TH/seedminer.txt b/_pages/th_TH/seedminer.txt
index c99db98353..333617c42a 100644
--- a/_pages/th_TH/seedminer.txt
+++ b/_pages/th_TH/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/th_TH/troubleshooting.txt b/_pages/th_TH/troubleshooting.txt
index 8a55c8ed04..33f0dd86f2 100644
--- a/_pages/th_TH/troubleshooting.txt
+++ b/_pages/th_TH/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/tr_TR/seedminer.txt b/_pages/tr_TR/seedminer.txt
index 5e675383b2..9daf655ee1 100644
--- a/_pages/tr_TR/seedminer.txt
+++ b/_pages/tr_TR/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/tr_TR/troubleshooting.txt b/_pages/tr_TR/troubleshooting.txt
index 3312192786..556eec5a2d 100644
--- a/_pages/tr_TR/troubleshooting.txt
+++ b/_pages/tr_TR/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/uk_UA/seedminer.txt b/_pages/uk_UA/seedminer.txt
index c99db98353..333617c42a 100644
--- a/_pages/uk_UA/seedminer.txt
+++ b/_pages/uk_UA/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/uk_UA/troubleshooting.txt b/_pages/uk_UA/troubleshooting.txt
index 8a55c8ed04..33f0dd86f2 100644
--- a/_pages/uk_UA/troubleshooting.txt
+++ b/_pages/uk_UA/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/vi_VN/seedminer.txt b/_pages/vi_VN/seedminer.txt
index c99db98353..333617c42a 100644
--- a/_pages/vi_VN/seedminer.txt
+++ b/_pages/vi_VN/seedminer.txt
@@ -21,6 +21,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
 1. Copy the 32 character long name of the folder you see inside Nintendo 3DS
   + Do not go inside any more folders
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/vi_VN/troubleshooting.txt b/_pages/vi_VN/troubleshooting.txt
index 8a55c8ed04..33f0dd86f2 100644
--- a/_pages/vi_VN/troubleshooting.txt
+++ b/_pages/vi_VN/troubleshooting.txt
@@ -253,9 +253,17 @@ Your device had custom firmware in the past, so you were not automatically promp
 The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
 {: .notice--info}
 
-### My device gets stuck on a black screen, and the blue light turns off
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-There is an issue with your `boot.firm` file (it is missing, misplaced, or corrupted). Download the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
 
diff --git a/_pages/zh_CN/seedminer.txt b/_pages/zh_CN/seedminer.txt
index dbb8c9e9f8..0ec7269a87 100644
--- a/_pages/zh_CN/seedminer.txt
+++ b/_pages/zh_CN/seedminer.txt
@@ -21,6 +21,7 @@ title: "Seedminer"
 1. 复制你在 Nintendo 3DS 文件夹内看到的 32 位字符文件夹的名称
   + 不要再点进任何文件夹
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/zh_CN/troubleshooting.txt b/_pages/zh_CN/troubleshooting.txt
index 703d07914e..c62cfa1b02 100644
--- a/_pages/zh_CN/troubleshooting.txt
+++ b/_pages/zh_CN/troubleshooting.txt
@@ -254,9 +254,17 @@ title: "问题排查"
 此处列出的操作方法将假设你的主机安装了最新的自制固件（boot9strap + Luma3DS 8.0 或更高版本）。 如果你的主机还在用旧版的自制固件（例如基于 arm9loaderhax 或 menuhax 的东西），则你应该在继续操作前先升级自制固件。
 {: .notice--info}
 
-### 主机开机只闪一下蓝灯
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-你放的 `boot.firm` 文件有问题（丢失、放错位置或者损坏）。 下载最新版本的 (https://github.com/LumaTeam/Luma3DS/releases/latest) 并将 `boot.firm` 放在你 SD 卡的根目录中，如有存在相同文件请替换。 请不要用 WinRAR 解压 ZIP 文件，我们目前已知这会导致与 3DS 有关的文件出错。
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 如果你在开机的时候听到了“啪”的一声，然后蓝灯熄灭，则代表你的主机可能有硬件上的问题了。（如：背光排线断开） 你的主机或许能在开盖特定角度的情况下开机。
 
@@ -267,7 +275,7 @@ title: "问题排查"
 1. 将主机强制关机，拔出游戏卡带（若有），然后再次打开主机等待十分钟。 如果你的主机在十分钟内成功开机，则这个问题就自行修复了，且不太会再次发生
 1. 将 SD 卡上的 `Nintendo 3DS` 文件夹重命名为 `Nintendo 3DS_BACKUP`，然后尝试启动主机。 如果成功开机了，则 `Nintendo 3DS` 文件夹有问题。 尝试清理主菜单的外部存储文件：
 	+ 进入到 `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
-  + Delete the corresponding folder for your 3DS region: 
+  + 删除对应你的 3DS 区域的文件夹： 
 		+ **欧版**: `00000098`
 		+ **日版**: `000000082`
 		+ **美版**: `000008f`
diff --git a/_pages/zh_TW/seedminer.txt b/_pages/zh_TW/seedminer.txt
index c2740b29b8..7fe1947e18 100644
--- a/_pages/zh_TW/seedminer.txt
+++ b/_pages/zh_TW/seedminer.txt
@@ -21,6 +21,7 @@ title: "Seedminer"
 1. 複製您在Nintendo 3DS 資料夾看到的32個字元長的資料夾名稱
   + 請不要再點擊任何一個資料夾
   + If you see multiple 32 character long folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
+  + You can ignore the `private` folder if you have it
 
 	![]({{ "/images/screenshots/id0-example.png" | absolute_url }})
 	{: .notice--info}
diff --git a/_pages/zh_TW/troubleshooting.txt b/_pages/zh_TW/troubleshooting.txt
index c492ef2a1f..e7e92c0460 100644
--- a/_pages/zh_TW/troubleshooting.txt
+++ b/_pages/zh_TW/troubleshooting.txt
@@ -253,9 +253,17 @@ Back up your data and reformat your SD card as FAT32 with the recommended tool d
 此處列出的步驟將假設你的主機安裝了最新的自製韌體(boot9strap + Luma3DS 8.0 或更高版本)。 如果你的主機還在用舊版的自製韌體(例如基於 arm9loaderhax 或 menuhax 的安裝)，則你應該在繼續操作前先升級自製韌體。
 {: .notice--info}
 
-### 主機開機只閃一下藍燈，且什麼都沒出現
+### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
 
-您所使用的 `boot.firm` 檔案有問題(如遺失、放錯位置或者損壞)。 下載最新版本的 (https://github.com/LumaTeam/Luma3DS/releases/latest) 並將 `boot.firm` 放在你 SD 卡的根目錄中，如有存在相同檔案請直接覆蓋。 請不要用 WinRAR 解壓 ZIP 檔案；目前已知使用此軟體會導致與 3DS 有關的檔案的問題。
+There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
+
+If the notification LED flashes:
+
+- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
+- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
+- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
+
+You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
 
 如果你在開機的時候聽到了“啪”的一聲，然後藍燈熄滅，則代表你的主機可能有硬體上的問題(如：背光排線斷開)。 你的主機或許能在開蓋特定角度的情況下開機。