Nand/private/movable.sed: Difference between revisions

← Older edit Newer edit →

@@ Line 25: / Line 25: @@
 |}
-This file is transferred to the destination 3DS during a [[System Transfer]], the source 3DS then uses a new file retrieved from the shop server. The keyslots this keyY is loaded to is the keyslots used for SD data. This keyY is the console-unique portion of these 3 keyslots. One of the keyslots initialized by this, is used for SD/NAND [[extdata]]. It's unknown where the first 8-bytes of the keyY is loaded from.
+This file is transferred to the destination 3DS during a [[System Transfer]], the source 3DS then uses a new file retrieved from the shop server. This keyY is the console-unique portion of these 3 keyslots. All of the data under [[SD Filesystem|sdmc/Nintendo 3DS/<ID0>/<ID1>]] and [[Flash Filesystem|nand/data/<ID0>]] use these console-unique keyslots. It's unknown where the first 8-bytes of the keyY is loaded from.
-The keyY is hashed with SHA256, the first 0x10-bytes from the hash is used for the SD card hex directory name under "/Nintendo 3DS/".
+Movable.sed always exists on retail, however if this file doesn't exist the system will fall-back to using a console-unique keyY already in memory. Therefore, movable.sed presumably doesn't exist on development units.
+The keyY is hashed with SHA256, the first 0x10-bytes from the hash is used for ID0 in [[SD Filesystem|sdmc/Nintendo 3DS/<ID0>/<ID1>]] and [[Flash Filesystem|nand/data/<ID0>]].