Hi, I have some questions/suggestions regarding 3DS.Guide with Boot9strap. I didn't know where to post, is there a 3DS.Guide official thread on gbatemp? I'm not familiar with 3DS as I didn't follow this section for the past 2 years, so I might be wrong but they are remarks I have after reading all the guides. I just took interest in 3DS.guide this weekend, I don't know what was written there before. First questions are for @Plailect • 3ds.guide is missing information specifically for gateway users. - the guide does not tell users that gateway will be unusable after following the guide, due to updating to latest version. - The guide does not tell users to backup the gateway saves BEFORE following the guide (there's only a link in the FAQ), or it will not be possible anymore (unless gateway release a new launch method for 11.x) - @lafleche made a thread about gateway, I have similar concerns. but I created this thread because I have more questions. - The guide tell users on a 4.x firmware to "delete the file later", but it would be nice to have a reminder at the update step to delete these files if they were used. (just to be safe, is it problematic to keep them for next steps?) • Question about the guide itself it concerns the "Otherapp" homebrew launcher. in the finalizing part, section I, point 13-14, it tells o3DS users to get "The Old 3DS 11.2.0-35" and rename it to "match your region", but the example also has an updated version number "OLD-11-4-0-37-REGION.bin". this step is confusing : do we have to download "11.4" instead of "11.2" ? or do we have to download "11.2" and rename it to "11.4" and never touch it again ? or do we have to download "11.2", rename it to "11.4" but also rename the filename to match the future existing version Luma is running after doing a FW update (11.5, etc) ? This part is used to launch the homebrew launcher from an option within Luma? Why not install a homebrew launcher cia and not use a specific payload? That step is confusing to me, probably because I didn't follow homebrew launcher issues with new firmware updates. • 3DS guide is missing some glossary - There's no mention to what CTRNAND is, especially when reaching the step "CTR NAND Luma" All the guide is using "NAND" or sysNAND, and at this steps is start using "CTR NAND" name. is it the same thing? one question about it : Is it adding .firm or replacing an existing/official one? - what is DSP ? what is the "Section VI - DSP Dump" useful for? - some users are asking "what is OTP?" too. I know, but some users don't. • in 3DS.Guide troubleshooting There's a mention to "DSI/NDS don't work anymore" is it common and every users have to update their TWL/NDS firmware files after completing the guide, or it only concerns specific users coming from specific 3DS firmware? I'm on 4.5.0-5, can I know if I will be affected before or do I have to just test it and see if I need this fix? • EmuNAND restoring to SysNAND When following this step, all the data on sysNAND will be replaced with the emuNAND one? you will lose data, settings, installed games or it will merge emuNAND to sysNAND without losing sysNAND existing data/savegames/extData? Is there a difference with linked or unlinked emuNAND? Would you lose your sysNAND extData if you had unlinked NANDs? What I understand is : backup DSI/GBA save, replace sysNAND with emuNAND, restore backup of DSI/GBA to the sysNAND. is there a way to backup/restore sysNAND extData too? If there were DSI/GBA already on emuNAND and they are in collision with the restored one, what would happen? • Gateway Save conversion linked in 3DS.guide faq This one concerns @MattKimura's guide. I'm post it here as I have questions after reading the new 3DS.guide, but if you'd prefer I can post it in your guide instead. The FAQ on 3DS.guide links to this save converter guide. I see it was written few months ago, so maybe it's not up to date with current guide? • it says "for users who want to keep using gateway AND cfw", I guess you can't use gateway anymore if you followed the new 3DS.Guide So, you need to do it BEFORE following 3DS.guide/before updating the firmware. • I think the guide is missing some steps. in one of the step, there is "press Select to open gateway menu", which imply the user should already be in Gateway mode. But nowhere in the guide it was said to boot gateway menu. should the user with gateway emuNAND be doing the conversion on sysNAND? (use an SD card without emuNAND partition, or boot gateway in sysNAND mode) That would prevent installing and initializing the cia savegame on both emuNAND and sysNAND? • The cia savegame is stored on SD or NAND? (I never used cia) I suppose only the "external data" is stored on external device, so cia games are stored on NAND, right? so if you convert gateway to CIA, you'll have to backup cia savegame on emuNAND to put them on sysNAND later? how to do it? • Users following 3DS.guide are suggested to use sysNAND instead of EmuNAND, so at the end, all the data has to be on sysNAND. I remember some data had deletion issue when visiting the data manager menu on sysNAND when using emuNAND. ExtData is on SD, but you mentioned "if you use the same NAND you are fine", is it based on whether the user linked/unlinked its sysNAND/emuNAND? Will the extData used in emuNAND still work fine on linked sysNAND? Will the extData used in emuNAND still work fine on unlinked sysNAND? how to convert extData to another NAND? godmod9? - I don't understand the need to put the current savegame to convert on the root of the SD card and renaming it to JKSM's save filename. that would be useful only in case gateway is actually "mounting" a JKSM.3DS file, as it would put the 0004000002C23200.sav into gateway's SRAM, but you are not launching JKSM with gateway, you are launching it from cia. I don't see when the "0004000002C23200.sav" is actually decrypted. The guide tells to : - mount the game you want to convert in gateway <select> menu. it's putting that original game's <gameID>.sav into the gateway's SRAM. (not 0004000002C23200.sav) - run JKSM to "dump the cartridge SRAM" to a user specified filename (so it's not saving the cartridge SRAM 0004000002C23200.sav ? if it were you wouldn't have to put it there manually as it would overwrite that file) - in JKSM, select "restore the newly created savegame to CIA" I didn't use JKSM yet, so I imagine when you choose a "date" (5-8-16 in your example) it doesn't create a new file on SD card, but store that data inside the "0004000002C23200.sav" filename. so, 0004000002C23200.sav can contains multiple savegames? it contains the unencrypted version of the "extracted flashcard's SRAM", but what happened to the original gateway backup renamed to that filename?