3DS:Ctrcheck: Difference between revisions
From Hacks Guide Wiki
More actions
adjust translation tags, especially for info template; correctly categorize |
use Template:ml where needed |
||
| Line 16: | Line 16: | ||
ctrcheck does not fix the majority of issues by itself, and instead only informs the user that they exist. Some of the issues it checks for may still require large amounts of knowledge to fix - this script is not a 'miracle cure' and should not be treated as such. | ctrcheck does not fix the majority of issues by itself, and instead only informs the user that they exist. Some of the issues it checks for may still require large amounts of knowledge to fix - this script is not a 'miracle cure' and should not be treated as such. | ||
Additionally, ctrcheck cannot check whether the SD is damaged, only certain specific issues with reading its data. If you have an issue that might be caused by an SD being corrupted or formatted badly, the pages | Additionally, ctrcheck cannot check whether the SD is damaged, only certain specific issues with reading its data. If you have an issue that might be caused by an SD being corrupted or formatted badly, the pages {{ml|Formatting an SD card}} and/or {{ml|Checking SD card integrity}} will be far more useful. | ||
== Instructions == | == Instructions == | ||
| Line 42: | Line 42: | ||
# <translate>Accept any prompts to fix issues and unlock sysNAND write permissions that appear, perform data recovery and rerun the script if instructed to, and then read the results on the top screen once the script is entirely finished</translate> | # <translate>Accept any prompts to fix issues and unlock sysNAND write permissions that appear, perform data recovery and rerun the script if instructed to, and then read the results on the top screen once the script is entirely finished</translate> | ||
# <translate>If you are following this guide at someone else's request, send a copy of the results to that person. Otherwise, if the results include any of the following, do the matching instructions:</translate> | # <translate>If you are following this guide at someone else's request, send a copy of the results to that person. Otherwise, if the results include any of the following, do the matching instructions:</translate> | ||
#* <translate><code>______ installed to firm0/firm1</code>: If the result type is <code>Information</code>, you may ignore this line. If the type is <code>Warning</code> or <code>Critical</code>, follow either [[3dsguide:updating-b9s|Updating B9S]] (if using boot9strap) or | #* <translate><code>______ installed to firm0/firm1</code>: If the result type is <code>Information</code>, you may ignore this line. If the type is <code>Warning</code> or <code>Critical</code>, follow either [[3dsguide:updating-b9s|Updating B9S]] (if using boot9strap) or {{ml|3DS:Fastboot3DS/Usage#Updating_fastboot3DS|Updating fastboot3DS}} (if using fastboot3DS) to get the latest version of a known good bootloader. If the type is <code>Error</code> and both FIRM0 and FIRM1 are affected, ask for help in the {{ml|Get support|Nintendo Homebrew Discord}}</translate> | ||
#* <translate><code>Critical: NVRAM is inaccessible</code>: If your console is an old model (no ZL/ZR shoulder buttons and no C-Stick), try reseating the Wi-Fi module on the motherboard. If this does not fix it or you have a new model, download this [[Special:DownloadWithFilename/File:Luma ignore cfgnor.firm/boot.firm| special build of Luma]] and put it on the root of your SD card, replacing <code>boot.firm</code> if it already exists</translate> | #* <translate><code>Critical: NVRAM is inaccessible</code>: If your console is an old model (no ZL/ZR shoulder buttons and no C-Stick), try reseating the Wi-Fi module on the motherboard. If this does not fix it or you have a new model, download this [[Special:DownloadWithFilename/File:Luma ignore cfgnor.firm/boot.firm| special build of Luma]] and put it on the root of your SD card, replacing <code>boot.firm</code> if it already exists</translate> | ||
#** <translate>This build does not fix the issue, only stop it from causing system crashes. You will still be unable to play DS games, and if you were unable to use Wi-Fi it will also stay broken - fixing these entirely requires a hardware replacement</translate> | #** <translate>This build does not fix the issue, only stop it from causing system crashes. You will still be unable to play DS games, and if you were unable to use Wi-Fi it will also stay broken - fixing these entirely requires a hardware replacement</translate> | ||
| Line 48: | Line 48: | ||
#* <translate><code>Warning: There is no boot.firm/boot.3dsx in the SD card root</code>: Follow [[3dsguide:restoring-updating-cfw|Restoring / Updating CFW]] to reacquire the file(s)</translate> | #* <translate><code>Warning: There is no boot.firm/boot.3dsx in the SD card root</code>: Follow [[3dsguide:restoring-updating-cfw|Restoring / Updating CFW]] to reacquire the file(s)</translate> | ||
#* <translate><code>Critical: NAND is unreadable at _______...?</code>: Your console's internal storage is damaged in a way that may require advanced troubleshooting to fix. Ask for help in the {{ml|Get support|Nintendo Homebrew Discord}}</translate> | #* <translate><code>Critical: NAND is unreadable at _______...?</code>: Your console's internal storage is damaged in a way that may require advanced troubleshooting to fix. Ask for help in the {{ml|Get support|Nintendo Homebrew Discord}}</translate> | ||
#* <translate>One or more of movable.sed, LFCS, SecureInfo, and/or HWCAL is marked as either <code>invalid</code> or <code>still invalid after a recovery attempt</code>: If you have a NAND backup from before this happened, | #* <translate>One or more of movable.sed, LFCS, SecureInfo, and/or HWCAL is marked as either <code>invalid</code> or <code>still invalid after a recovery attempt</code>: If you have a NAND backup from before this happened, {{ml|3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore it}}. If you do not, then ask for help in the {{ml|Get support|Nintendo Homebrew Discord}}</translate> | ||
#* <translate><code>Critical: n3DS has an o3DS NAND header</code>: If you have a NAND backup from before this happened, | #* <translate><code>Critical: n3DS has an o3DS NAND header</code>: If you have a NAND backup from before this happened, {{ml|3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore it}}. If you do not, then ask for help in the {{ml|Get support|Nintendo Homebrew Discord}}</translate> | ||
# <translate>If any other result(s) of the type <code>Warning</code>, <code>Critical</code>, or <code>Error</code> appear, you may want to ask for help in the {{ml|Get support|Nintendo Homebrew Discord}} and provide the full output of ctrcheck there</translate> | # <translate>If any other result(s) of the type <code>Warning</code>, <code>Critical</code>, or <code>Error</code> appear, you may want to ask for help in the {{ml|Get support|Nintendo Homebrew Discord}} and provide the full output of ctrcheck there</translate> | ||
{{info|text=<translate>The results found on the top screen are also stored on the SD card in the file <code>sd:/gm9/ctrcheck_latest.txt</code> - however, if you run ctrcheck again, that file will be overwritten with the new results. To avoid this, enabling permanent logging will also append the results to the file <code>sd:/gm9/ctrcheck_log.txt</code>.</translate>}} | {{info|text=<translate>The results found on the top screen are also stored on the SD card in the file <code>sd:/gm9/ctrcheck_latest.txt</code> - however, if you run ctrcheck again, that file will be overwritten with the new results. To avoid this, enabling permanent logging will also append the results to the file <code>sd:/gm9/ctrcheck_log.txt</code>.</translate>}} | ||