3DS:Ctrcheck: Difference between revisions

3DS:Ctrcheck (view source)

Revision as of 09:08, 23 September 2024

304 bytes added , 2 months ago

3.1.0, plus revised in-line troubleshooting to match the update

StarlitSkies

Approver, confirmaccount

398

edits

@@ Line 3: / Line 3: @@
 | for3ds = 1
 | developers = StarlitSkies, FrozenFire
-| version = 3.0.1
+| version = 3.1.0
-| releasedate = 2024-09-17
+| releasedate = 2024-09-23
 | website = https://gist.github.com/StarlitSkies/f417c1ded9de8fceffdb532f92823377/ gist.github.com
 }}
@@ Line 36: / Line 36: @@
 # Hold {{B|START}}, and while holding {{B|START}}, power on your console. This will launch GodMode9
 # Press the {{B|HOME}} button, then go into '''Scripts...''' -> '''ctrcheck'''
-#* If ctrcheck does not appear here, [[FILEXT|enable file extensions]] and then make sure the name of the script is exactly <code>ctrcheck.gm9</code>
+#* If ctrcheck does not appear here, go into the folder <code>0:/gm9/scripts</code> and manually rename it to <code>ctrcheck.gm9</code> by highlighting it and pressing {{B|R|X}}, then reopen the scripts menu
-# Based on the type of issue you're having, select one of the top four options
+# Based on the type of issue you're having, select one of the top three options
-#* If you are even slightly unsure about what type of issue it is, pick '''Full'''
+#* If you are even slightly unsure about what type of issue it is, pick '''All'''
 # Accept any prompts to fix issues and unlock sysNAND write permissions that appear, then read the results on the top screen once the script finishes
 # If you are following this guide at someone else's request, send a picture of the results to that person. Otherwise, if the results include any of the following, do the matching instructions:
-#* <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 [[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>, ask for help in the [[Get support|Nintendo Homebrew Discord]]
+#* <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 [[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 [[Get support|Nintendo Homebrew Discord]]
 #* <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 [[Media:Luma_v13.0.2_ignore-cfgnor.firm|the]] special build of Luma linked in the fourteenth word of this sentence, rename it to <code>boot.firm</code>, and put it on the root of your SD card
 #** 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
@@ Line 47: / Line 47: @@
 #* <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)
 #* <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 [[Get support|Nintendo Homebrew Discord]]
-#* <code>Bruh Moment: movable.sed is from Seedminer</code>: You have made a mistake. [[3DS:Recover_movable.sed|Find your original movable]] and restore it to the folder <code>1:/private</code>, or else uninstalling CFW will be guaranteed to brick your console. If you cannot find your original movable, ask for help in the [[Get support|Nintendo Homebrew Discord]] and provide every piece of context you know about this issue
+#* One or more of movable.sed, LFCS, SecureInfo, and/or HWCAL is marked as <code>not found</code>, <code>is an invalid size</code>, or <code>data is invalid</code>: If you have a NAND backup from before this happened, [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore it]]. If you do not, then ask for help in the [[Get support|Nintendo Homebrew Discord]]
-#* 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 [[Get support|Nintendo Homebrew Discord]] and provide the full output of ctrcheck there
+#* <code>Critical: n3DS has an o3DS NAND header</code>: If you have a NAND backup from before this happened, [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore it]]. If you do not, then ask for help in the [[Get support|Nintendo Homebrew Discord]]
-{{info|text=The results of this ctrcheck can also be found on the SD card in <code>sd:/gm9/ctrcheck_latest.txt</code> - however, if you run ctrcheck again, this file will be overwritten with the new results. If permanent logging was enabled, it will also be appended to the file <code>sd:/gm9/ctrcheck_log.txt</code>.}}
+# 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 [[Get support|Nintendo Homebrew Discord]] and provide the full output of ctrcheck there
+{{info|text=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>.}}
 [[Category:Unbricking]]
 [[Category:Nintendo 3DS troubleshooting]]