3dbrew

Bootloader: Difference between revisions

← Older editNewer edit →
Xcution (talk | contribs)
157 edits
No edit summary
3dsguy (talk | contribs)
839 edits
No edit summary
Line 9: Line 9:
* 2 Seconds - bootloader attempts to initialize the NAND. If the NAND is successfully initialized, it takes over booting the 3DS. If the NAND, cannot be initialized (i.e. the NAND chip is not connected/damaged etc) a blue error screen similar to the screen above appears.
* 2 Seconds - bootloader attempts to initialize the NAND. If the NAND is successfully initialized, it takes over booting the 3DS. If the NAND, cannot be initialized (i.e. the NAND chip is not connected/damaged etc) a blue error screen similar to the screen above appears.


* 3 Seconds - all essential hardware is active - checks all connected devices and will boot the slot 1 device if it is an auto-boot card(like kiosk demos etc). The home menu has not initialized at this point as auto-booted games by-pass certain [[Home Menu]] security measures, like parental control and forced updates. Also auto-booted games are not logged as being run from the [[Home Menu]]. Begins to initialize [[Home Menu]] if an auto-boot slot1 device is not found.
* 3 Seconds - all essential hardware is active - [[NS]] loads the [[Shared_Registers#REG_ACTIVEMENUTID|current active menu]], for retail units this is usually the [[Home Menu]].
Autoboot devices do not appear to bypass the region lock. (yields "An Error has Occurred" if out-of-region demo)


* 4 Seconds - the LCD screens are initialized
* 4 Seconds - the LCD screens are initialized


* 7 Seconds - [[Home Menu]] is fully initialized/loaded
* 7 Seconds - [[Home Menu]] is fully initialized/loaded
Retrieved from "https://www.3dbrew.org/wiki/Bootloader"