Approver
42
edits
(Added a prefetch abort menu error on boot scenario after a helpee encountered it by enabling hbmenu autoboot to access menuhax67_installer.) |
(Fixed some formatting issues) |
||
Line 78: | Line 78: | ||
<h5>hid</h5> | <h5>hid</h5> | ||
* Potential hardware problems, or an outdated version of Rehid. | * Potential hardware problems, or an outdated version of Rehid. | ||
** First look for and delete <code>/luma/titles/0004013000001D02</code> and <code>/luma/titles/0004013000003302</code>. If these | ** First look for and delete <code>/luma/titles/0004013000001D02</code> and <code>/luma/titles/0004013000003302</code>. If these don't exist, or you've never downloaded Rehid, it's likely hardware issues. | ||
*** [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation. | *** [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation. | ||
Line 104: | Line 104: | ||
** An installation of menuhax is conflicting with the custom firmware. | ** An installation of menuhax is conflicting with the custom firmware. | ||
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]]. | *** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]]. | ||
**If this occurs on boot, enable hbmenu autoboot in the Luma configuration menu to 3DS mode, then follow above instructions | **If this occurs on boot, enable hbmenu autoboot in the Luma configuration menu to 3DS mode, then follow above instructions | ||
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root. | |||
***Turn hbmenu autoboot back off when menuhax67 is removed | |||
* <h6>prefetch abort (svcBreak)</h6> | * <h6>prefetch abort (svcBreak)</h6> | ||
** The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>. | ** The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>. |