Hacking [Release] AIO B9S Pack Lite (configurations include GW, simple A9LH to B9S upgrader included)

[Kazuma77]

Warning: Running Gateway on an 11.3 or higher SysNAND will either put you on retail or brick the device. It is heavily recommended to create an 11.2 (or partially updated 11.4) EmuNAND for running Gateway mode at this time. Note that Gateway mode requires you to have the red GW card. If you do not, you have nothing to worry about. For the same reason, do not run Cakes or Skeith until you have properly configured them, because the firm protection patch is optional in these CFWs. If you don't know which option to select, either consult the documentation on their release pages, or just don't use them.

The AIO B9S Pack is obsolete now, so it has been removed. Please find my InScripted AIO on that iso site in the "CFW Discussion" section. I see no point in releasing it here, because then it would no longer be an AIO.

InScripted does everything this did and much more. It includes installers -- both the same card "install and self-destruct" type, and a PC-less swap card. And all of those separate configurations are now unified, because you can switch chainloaders via scripts now. You can also switch the default payload in dedicated chainloaders via scripts now instead of having to rename files. There are even scripts to change the hotkeys now. No more trips to the PC to change your configuration. This is now more than just a collection of useful files. This release uses scripts to automate EVERYTHING for you. Hence the name.

I could put up the usual lengthy explanation, but, there are "ReadMe.txt" files in the pack. If you're interested, find the pack, download it, and read them. I'm simply going to list what's new here.


What's new in R5:


Improvements: Hotkey configuration via scripts is now possible thanks to the new "filesel" command in GM9. You can pick any payload you want for any hotkey in both BootCTR9 (in Select Mode) and Luma. Because of this, "BootCTR9 (Select Mode)" has now become the default chainloader, since it can now offers both the ability to switch the default payload and all hotkeys to anything included. I've added the hotkey options for Luma as well, but you obviously can't change the default payload. You can change all but one hotkey (because it needs to chain to the same BootCTR9-defined hotkey to work) in Luma, but converted payloads won't work (like I say, it's the best CFW, but the rxTools of chainloaders). I have included scripts for individual hotkeys and a "Change All Hotkeys" one (though despite it's name, you don't have to change all of them -- you can hit B to skip one you don't want to change, and the script will simply move on to the next hotkey).

I have added an unchangeable hotkey as a safety -- R (in Luma L+R). This is a standalone script runner version of the "Reset to Defaults" script in the "Default Payloads & Hotkeys" and "Hotkeys" script menus (depending on whether you're using BootCTR9 or Luma, respectively). This is in case you royally screw up and forget to hotkey Godmode9. Just hold R and once it reboots, the defaults are back.

Cakes Launcher is now a single script. With "filesel" providing the ability to simply pick the firmware file straight from the "cakes" folder, there is no more need to have a script for each firmware version supported. However, because of a problem with OldLoader and GM9 versions higher than 1.3.4, I had to keep the old version for use with A9LH (for now).

I have included a "Card Cleaner" batch file you can copy to the SD card and run to purge old versions of files that may get in the way of the new release working properly. I probably should have done this sooner, but this release particularly needs to purge old files because all of the Luma and Luma Legacy payloads have been renamed, so that they have no description (just a hotkey followed by an underscore). This was necessary to avoid duplicate hotkeys and ensure the scripts that configure said hotkeys function smoothly.

Removed the "Initial Setup" workaround that was supposed to be in both configurations (yet somehow only remained intact in the A9LH configurations, which all but defeated the purpose anyway) and removed all reference to it from the documentation. I decided the solution was worse than the problem. If there's anyone out there actually doing a manual dual exploit setup, just delete the "gm9/scripts" folder before copying the B9S configuration over (the installers take care of this automatically).

Made some minor improvements to the installers (and some alterations were needed to accommodate the other changes to the pack).

 

[nccom]

Nice, thanks for that pack and scripts! Will check it later, its always useful to have such power tools and not just only luma.

 

[xxfliermiles]

So there isn't a 11.2 EMUNAND set up for me yet (which is what we want to use to run this AIO set up right???)...

In that case, if all of the files on my SD Card (which host my .cia files that run on Luma 8.1 CFW - - - SYSNAND 1.5) is saved onto my HDD, is 'restoring' all of these files after re-formatting my SDCard to set up a EMUNAND partition as simple as dragging and dropping all of these prior files back onto the SD card?

Or is there a more elaborate restoration process than this?

 

[Kazuma77]

So there isn't a 11.2 EMUNAND set up for me yet (which is what we want to use to run this AIO set up right???)...

In that case, if all of the files on my SD Card (which host my .cia files that run on Luma 8.1 CFW - - - SYSNAND 1.5) is saved onto my HDD, is 'restoring' all of these files after re-formatting my SDCard to set up a EMUNAND partition as simple as dragging and dropping all of these prior files back onto the SD card?

Or is there a more elaborate restoration process than this?

Well, there's no way to create an EmuNAND you can just drag and drop to your card. NANDs tend to be console specific, and EmuNAND uses a raw partition before the primary FAT partition. Which means there is no way to create one without formatting the card.

And yes, all you need to do is copy the files. Just drag and drop. Actually, all of your installed content is in the "Nintendo 3DS" folder specifically. I believe you said you had two cards though. And that the second one did have the EmuNAND setup. So, if you copy your "Nintendo 3DS" folder from the first to the second, All of your installed content would be copied over.

You could copy, for example, the BootCTR9 configuration to either card, or even both. It will boot Luma by default, but Gateway would run if you hold B (assuming you already have Launcher.dat on the card). Of course, you don't want to run GW with an 11.5 SysNAND, so you would not want to hold B with the no-EmuNAND card in the system. Though fortunately GW will not boot straight to SysNAND without popping up a warning, so if you hit it by accident, you would be OK.

You'll notice there's a "boot_config_gw.ini" in the BootCTR9 folder. If you rename the existing "boot_config.ini" to "boot_config_luma.ini" and rename "boot_config_gw.ini" to "boot_config.ini" it will boot Gateway by default. You were saying before that you wanted to setup a separate card just for Gateway. So, this would work for that. Though it's not really necessary to do that. You can have both on the same card. Just have the one you use the most boot by default, and place the other on a hotkey (if you make GW the default, Luma will still be available by holding A when you turn the system on).

Of course, that's just how I have it configured. These .ini and .cfg files are plain text files. It's easy to modify the hotkey/menu layout. You can also delete options you won't use if you like. I just put everything on these because it's easier to delete lines you don't need than add ones that are missing.

 

[xxfliermiles]

You can have both on the same card. Just have the one you use the most boot by default, and place the other on a hotkey (if you make GW the default, Luma will still be available by holding A when you turn the system on).

I'm thinking of having SYSNAND 11.5 & EMUNAND 11.2 on the same card, so Let's forget about the other SD card for a moment since it may Not Be As UsefuL As first thought (can't use it at the moment cus SYSNAND 11.5 is my Default...)

Anyway, just sum questions:

A) is it necessary for me to use the save-data-backup-management (from within system settings) to back up the save files for all my .cia files in order to re store them Later?

or will these files be saved just by copying and pasting all folders & files of my SD card onto my HDD, and then after formatting a EMUNAND partition, these files can be pasted back tO their original LocatioNs???

B - - - & SecunDLY,

Once the cloning of my SYSNAND 1.5 CFW - - - > EMUNAND 1.5 CFW takes effect on my single SD card, will there be two or more different areas on the root of my SD card whicH pertain to each NAND?

 

[Kazuma77]

I'm thinking of having SYSNAND 11.5 & EMUNAND 11.2 on the same card, so Let's forget about the other SD card for a moment since it may Not Be As UsefuL As first thought (can't use it at the moment cus SYSNAND 11.5 is my Default...)

Anyway, just sum questions:

A) is it necessary for me to use the save-data-backup-management (from within system settings) to back up the save files for all my .cia files in order to re store them Later?

or will these files be saved just by copying and pasting all folders & files of my SD card onto my HDD, and then after formatting a EMUNAND partition, these files can be pasted back tO their original LocatioNs???

B - - - & SecunDLY,

Once the cloning of my SYSNAND 1.5 CFW - - - > EMUNAND 1.5 CFW takes effect on my single SD card, will there be two or more different areas on the root of my SD card whicH pertain to each NAND?

A) Not at all. The games, apps, saves, themes, and anything else that isn't either part of the firmware or a DSiWare title/save (which are stored on the system) is stored in the "Nintendo 3DS" folder. Nintendo has done nothing to prevent you from backing it up because it's encrypted and tied to your system. In fact, they openly encourage you to transfer your data to a bigger card so they can sell you more games on the eShop.

While you're at it, you might even want to create two EmuNANDs if you have plenty of space. You could put 9.2 on the second one and use it for any homebrew that won't work with Rosalina (you could even put Menuhax on it so it goes straight to the homebrew menu). Many CFWs support up to 4 EmuNANDS after all. Luma doesn't seem to like 9.2, but Puma does. That's my main reason for including it, and putting it on the Y key, right next to the GW option. You can have a setup where you do nothing for Luma on 11.5, hold B for GW on 11.2 (or partial 11.4), and hold Y for homebrew on 9.2.

B). Well, SysNAND is on the system itself. It's why your system can boot without an SD card. So nothing pertaining to that directly will be on the card. The EmuNAND(s) you create are a clone of the system's internal storage, and will be stored in a raw partition on the first part of the card, before the Fat32 paritition. You will not see drive letters for them on your PC, just the Fat32 partition. Apps like EmuNAND Tool or 3DS Multi EmuNAND Creattor can properly detect, read, and write them. But they'll be completely invisible to apps like Windows Explorer or Total Commander.

Just to clarify, games, apps, etc. don't get installed to NANDs. They get installed to a folder named for the current ID (think of it as a user profile) in the "Nintendo 3DS" folder. The NAND itself only stores the tickets and ID info (and DSiWare). When you unlink by formatting the system on a SysNAND or EmuNAND (or using an app like TinyFormat, which lets you keep your DSiWare, and doesn't try to format the SD card), it creates a different ID, so, titles installed in one will not show up in the other (the process is not random, either, so if you format both the same number of times, they're linked). So, you would have two folders within the "Nintendo 3DS" folder, one for each ID. If you keep them linked, there will just be one. But you will need to copy your tickets back and forth, or install the games twice, to get the tickets on both NANDs, or they'll only show up on one, get repackaged when switching back and forth, etc. I've included Godmode9 scripts to sync tickets though. Oh, and if you're having difficulty telling which NAND is which with them linked, the one thing they don't share is folders, so, you can create one called "EmuNAND" to tag your EmuNAND as such.

Also, neither SysNAND nor EmuNAND is tied to GW/CFW. Any CFW that supports EmuNAND and the firmware version it's on can boot your EmuNAND. Since GW can't boot your 11.5 EmuNAND, you will have to do this in order to downgrade it. Hold L at startup to launch it with Luma, then you can install SysUpdater and use it to install 11.2 (make sure you have the 11.2 files in a folder named "updates" on the card). And make sure you hit the downgrade button, because the update one will only install titles that are newer than the current version (seems obvious enough, but I've made that mistake before).

 

[xxfliermiles]

Also, neither SysNAND nor EmuNAND is tied to GW/CFW. Any CFW that supports EmuNAND and the firmware version it's on can boot your EmuNAND. Since GW can't boot your 11.5 EmuNAND, you will have to do this in order to downgrade it. Hold L at startup to launch it with Luma, then you can install SysUpdater and use it to install 11.2 (make sure you have the 11.2 files in a folder named "updates" on the card). And make sure you hit the downgrade button, because the update one will only install titles that are newer than the current version (seems obvious enough, but I've made that mistake before).

Ok if my memory serves me correctly, my 2ND SD Card (which is EMUNAND 11.2) uses menu hax to Auto Boot GW (me thinks)...

So how can one Boot this EMUNAND 11.2 safely when using Luma 8.1 SYSNAND CFW 11.5?

You use BootCTR9 to Boot into the EMUNAND 11.2 on the 2ND SD Card and then run GW's Launcher.dat?

If that is the case how do you launch BootCTR9 on the 2ND Card Card if there are no .cia files or homebrew launchers which are LUMA 8.1 compatible on it?

Finally, if its true that my 2ND SD Card does use menuhax to autoboot to gateway (BACK when my SYSNAND was 9.2)...

is it safe to get rid of those autoboot files which are: menuhax_padcfg.bin, ropbinpayload_menuhax_USA12288_old3ds.bin, boot.3dsx, boot_previous.3dsx right???

and just Leave LAUNCHEr.Dat on my 2ND SD Card ONLY if my goal is to ONLY use BootCtr9 on my 2ND SD Card to Boot the EMUNAND 11.2 from my 2ND SD Card then to launch the GW Launcher.Dat fiLe after?

 

[Kazuma77]

Ok if my memory serves me correctly, my 2ND SD Card (which is EMUNAND 11.2) uses menu hax to Auto Boot GW (me thinks)...

So how can one Boot this EMUNAND 11.2 safely when using Luma 8.1 SYSNAND CFW 11.5?

You use BootCTR9 to Boot into the EMUNAND 11.2 on the 2ND SD Card and then run GW's Launcher.dat?

If that is the case how do you launch BootCTR9 on the 2ND Card Card if there are no .cia files or homebrew launchers which are LUMA 8.1 compatible on it?

Finally, if its true that my 2ND SD Card does use menuhax to autoboot to gateway (BACK when my SYSNAND was 9.2)...

is it safe to get rid of those autoboot files which are: menuhax_padcfg.bin, ropbinpayload_menuhax_USA12288_old3ds.bin, boot.3dsx, boot_previous.3dsx right???

and just Leave LAUNCHEr.Dat on my 2ND SD Card ONLY if my goal is to ONLY use BootCtr9 on my 2ND SD Card to Boot the EMUNAND 11.2 from my 2ND SD Card then to launch the GW Launcher.Dat fiLe after?

OK, if it was using Menuhax, then that is why it is not working now. It does not have the files it needs. You need B9S files for a B9S system. Yes, you can take those files off the card. You might want to keep a backup of them in case you ever decide to do a second EmuNAND for 9.2. But yes, all you need to already have on the card is the "Launcher.dat" because the contents of the "BootCTR9" folder will cover the rest.

And you do not have a Luma 8.1 SysNAND. CFW is tied to nothing. Not your NANDs, and not your CIAs. Nothing is specific to any CFW. What you have is a B9S SysNAND on 11.5. That SysNAND can be booted by any CFW that supports 11.5, including Luma Legacy (which is based on 7.1), Skeith, ReiNAND, Cakes, and Puma.

A B9S-modified system looks for "boot.firm" when it boots. It doesn't have to be Luma. It could be any other CFW. It could even be Godmode9 (but then that's all the system would run, so, not a good idea). Now, Luma has what is called a chainloader built-in that allows you to launch other things with it. But it's not the only chainloader out there. BootCTR9 and CBM9 are very good chainloaders. And they often tend to be better because that's all they do. BootCTR9 is the "boot.firm" in this case, so, Luma would not even have to be on the card at all. Instead of renaming, it uses a configuration file to tell it what to load. That file is "boot_config.ini" and it is in plain text if you want to modify it. I have Gateway setup on "B" in "boot_config.ini" so if you boot while holding "B" it should boot Gateway into your 11.2 EmuNAND (assuming the red GW card is in the slot).

Just try it. Copy the contents of the BootCTR9 folder over to the card. Hold "B" while booting and see if it boots into Gateway mode. If that works, then all you need to do to make GW the default is replace "boot_config.ini" with "boot_config_gw.ini" because I've made Gateway the default in that copy.

 

[xxfliermiles]

Just try it. Copy the contents of the BootCTR9 folder over to the card. Hold "B" while booting and see if it boots into Gateway mode. If that works, then all you need to do to make GW the default is replace "boot_config.ini" with "boot_config_gw.ini" because I've made Gateway the default in that copy.

Ok it works, But not without errors. For example, if after Booting into EMUNAND 11.2 and going to system settings, it crashes Before returning to the home screen and says:

An error has occurred:
Launched from an unsupported location:
Press any button to shutdown

But other than that error, your AIO works great, even when we switch boot_config.ini to boot_config_gw.ini so that way B doesn't have to be held when my 2ND SD Card is in...

So even though running 11.5 SYSNAND and 11.2 EMUNAND frum just my first SD card seems appealing and hella efficient, using my 2ND SD Card just for 11.2 EMUNAND at least puts my 2ND SD card to use (otherwise there aren't much other useful devices to use a 4GB SD Card wit ANyway!

--------------------- MERGED ---------------------------

Ok so wen boot_config_gw.ini is made into boot_config.ini, when exiting the system settings app my 3DS just re-boots GW, but otherwise there aren't any errors (so maybe when using the default boot_config.ini its necessary for me to HOLD B wen exiting system settings??? (but is there anyway to prevent the existing of the system settings app from re-booting my 3DS)?

 

[Kazuma77]

Ok it works, But not without errors. For example, if after Booting into EMUNAND 11.2 and going to system settings, it crashes Before returning to the home screen and says:

An error has occurred:
Launched from an unsupported location:
Press any button to shutdown

But other than that error, your AIO works great, even when we switch boot_config.ini to boot_config_gw.ini so that way B doesn't have to be held when my 2ND SD Card is in...

So even though running 11.5 SYSNAND and 11.2 EMUNAND frum just my first SD card seems appealing and hella efficient, using my 2ND SD Card just for 11.2 EMUNAND at least puts my 2ND SD card to use (otherwise there aren't much other useful devices to use a 4GB SD Card wit ANyway!

--------------------- MERGED ---------------------------

Ok so wen boot_config_gw.ini is made into boot_config.ini, when exiting the system settings app my 3DS just re-boots GW, but otherwise there aren't any errors (so maybe when using the default boot_config.ini its necessary for me to HOLD B wen exiting system settings??? (but is there anyway to prevent the existing of the system settings app from re-booting my 3DS)?

It's a minor bug with Luma and BootCTR9. It has to do with the reboot patches or something. The problem should be solved by a future release of BootCTR9. There's a newer one out that already eliminates the error, but I can't get it to boot any text mode apps like Godmode9 and Decrypt9, so, a case where the cure is worse than the poison. And I've tried compiling it myself, but the resulting file doesn't work, so, either I'm doing something wrong, or the source hasn't been updated to the B9S 1.2 code yet. It only gives the error seemingly at random when rebooting Luma. If it really bothers you, you could use the Luma configuration. Same hotkey layout. That only uses BootCTR9 for GW, Puma, and Cakes, so, the error should not show up. However, then you are stuck with Luma as the default, because it's Luma's chainloader being used. Not that most are going to care, because they prefer Luma be the default anyway. I'm one of the few that will switch depending on what games I'm working on.

Exiting System Settings always reboots the device. It's how the system is designed to work. People have been asking that question since EmuNAND came out. Luma has a "persistence" feature where it will reboot to the same NAND you chose last (unless you hold A, then it resets to your default). That's the closest we're going to get I think. So, yes, if you go into System Settings in GW, and you want to reboot to GW, you need to hold B if you're using my original "boot_config.ini" file. You can still boot Luma with the GW one, btw. Just hold A. The same issue applies -- it will reboot back to GW unless you hold A when exiting System Settings.

 

[onnihs]

@Kazuma77

Hi,

I used your R5 package to install b9s on my O3DS on fw4.2 (and gw emunand on 10.2), all went ok but at the end of step 7 in the one & done instructions my 3ds rebooted (as it should have if I got it right) and I can see 3 new apps installed but they have a black icon and if I try to run them it keeps hanging on the 3DS logo; futhermore after exiting download play (end of step 8) instead of booting rosalina, it hangs on 3DS logo.
I think that maybe is due to my low firmware but before upgrading I wanted to ask you if it's safe to do so and if I should take some extra steps to get everything working.
I need to add that the hotkey shortcuts on boot work.
Thank you for your work (and in advance for your help )

 

[Kazuma77]

@Kazuma77

Hi,

I used your R5 package to install b9s on my O3DS on fw4.2 (and gw emunand on 10.2), all went ok but at the end of step 7 in the one & done instructions my 3ds rebooted (as it should have if I got it right) and I can see 3 new apps installed but they have a black icon and if I try to run them it keeps hanging on the 3DS logo; futhermore after exiting download play (end of step 8) instead of booting rosalina, it hangs on 3DS logo.
I think that maybe is due to my low firmware but before upgrading I wanted to ask you if it's safe to do so and if I should take some extra steps to get everything working.
I need to add that the hotkey shortcuts on boot work.
Thank you for your work (and in advance for your help )

Ah, it's probably an issue with 4.2. Older firmwares tend to work better when using an external "firmware.bin" as well. The manual recommends using 11.1. I did not include that one because Cakes doesn't support it, but 11.2 and the "cetk" file needed to decrypt it are in the "cakes" folder. Just copy them over and take the "112" off the filename (I'll include a decrypted 11.1 ready to rename in the O3DS configuration next update). Should fix the issue. You can also hold L to boot EmuNAND to test that theory. Since it's on 10.2, it should work alright. It is safe to update to 11.5. However, you may want to transfer your EmuNAND to SysNAND (I include a script for that, but it's easy to do manually too), then update to 11.5. Of course, then your NANDs would be linked. This can be useful if you have Gateway though, because you can update the EmuNAND to 11.2, and update the SysNAND to 11.5, and play the same games on both. You would need to synchronize tickets whenever you install games on one to get them to show up on the other (I include scripts for this), but, small price to pay if you have GW and use it for ROMs and/or the cheat engine. If you don't have Gateway, there's not so much of a reason to have linked NANDs, or even have an EmuNAND (I like to keep around a 9.2 so I don't have to wait for Ninjhax updates when an update comes out, but that's me).

If you don't have GW, and all the games are on your 10.2, you still might want to transfer it to SysNAND, and just delete EmuNAND, since this allows you to have your regular games, GBA, and DSiWare all on the same NAND, and eliminates an extra drain on your battery. Of course, deleting it means backing everything up, formatting the card, and copying everything back, so that 1 GB may not be worth it to you if you have a good sized card. What I did was back the NANDs up and just swap them (then when GW didn't update, I made a second one and moved my old 9.2 over since GW needed the first one). But like I said, I like having one on 9.2 for homebrew (I even put Menuhax on mine -- Rosalina crashes with it, but Legacy, Puma, and Cakes can run it fine) just so it can boot straight to the homebrew menu. If you do decide to delete it, like I said, make a backup just in case. Check for and backup any saves you want to keep as well.

I include a script for transferring EmuNAND to SysNAND without wiping your exploit (though GM9 also offers this option when you select a NAND backup). If you decide you want to restore the backup of SysNAND to EmuNAND, you could mount the image then copy nand_minsize.bin over to the E: drive. I'm adding NAND restore scripts in the next update (in hindsight, I probably should have wrote those before doing the hotkeys).

 

[onnihs]

Ah, it's probably an issue with 4.2. Older firmwares tend to work better when using an external "firmware.bin" as well. The manual recommends using 11.1. I did not include that one because Cakes doesn't support it, but 11.2 and the "cetk" file needed to decrypt it are in the "cakes" folder. Just copy them over and take the "112" off the filename (I'll include a decrypted 11.1 ready to rename in the O3DS configuration next update). Should fix the issue. You can also hold L to boot EmuNAND to test that theory. Since it's on 10.2, it should work alright. It is safe to update to 11.5. However, you may want to transfer your EmuNAND to SysNAND (I include a script for that, but it's easy to do manually too), then update to 11.5. Of course, then your NANDs would be linked. This can be useful if you have Gateway though, because you can update the EmuNAND to 11.2, and update the SysNAND to 11.5, and play the same games on both. You would need to synchronize tickets whenever you install games on one to get them to show up on the other (I include scripts for this), but, small price to pay if you have GW and use it for ROMs and/or the cheat engine. If you don't have Gateway, there's not so much of a reason to have linked NANDs, or even have an EmuNAND (I like to keep around a 9.2 so I don't have to wait for Ninjhax updates when an update comes out, but that's me).

If you don't have GW, and all the games are on your 10.2, you still might want to transfer it to SysNAND, and just delete EmuNAND, since this allows you to have your regular games, GBA, and DSiWare all on the same NAND, and eliminates an extra drain on your battery. Of course, deleting it means backing everything up, formatting the card, and copying everything back, so that 1 GB may not be worth it to you if you have a good sized card. What I did was back the NANDs up and just swap them (then when GW didn't update, I made a second one and moved my old 9.2 over since GW needed the first one). But like I said, I like having one on 9.2 for homebrew (I even put Menuhax on mine -- Rosalina crashes with it, but Legacy, Puma, and Cakes can run it fine) just so it can boot straight to the homebrew menu. If you do decide to delete it, like I said, make a backup just in case. Check for and backup any saves you want to keep as well.

I include a script for transferring EmuNAND to SysNAND without wiping your exploit (though GM9 also offers this option when you select a NAND backup). If you decide you want to restore the backup of SysNAND to EmuNAND, you could mount the image then copy nand_minsize.bin over to the E: drive. I'm adding NAND restore scripts in the next update (in hindsight, I probably should have wrote those before doing the hotkeys).

Yeah, when booting holding L the black icons disappear and opening download play boots HBL/Rosalina.
My ideal setup would be sysnand updated to latest fw (for cias and newer games in general) and gw emunand for .3ds roms and updates and dlcs for some games (I could keep it on 10.2 for that matter), so I don't think I need to link my NANDs since I would be using cias only on sys, nor copying my emunand to sysnand.
So if I got it right updating to 11.5 would be the next thing to do (which I could do by simply going to settings->update right?) , and then installing FBI, JKSM and freeshop from HBL/Rosalina that once, on 11.5, should work as expected.
Thank you and sorry for bothering but sometimes I feel overwhelmed from all this informations and not having followed the 3DS scene for some years only made this worse.

 

[Kazuma77]

Yeah, when booting holding L the black icons disappear and opening download play boots HBL/Rosalina.
My ideal setup would be sysnand updated to latest fw (for cias and newer games in general) and gw emunand for .3ds roms and updates and dlcs for some games (I could keep it on 10.2 for that matter), so I don't think I need to link my NANDs since I would be using cias only on sys, nor copying my emunand to sysnand.
So if I got it right updating to 11.5 would be the next thing to do (which I could do by simply going to settings->update right?) , and then installing FBI, JKSM and freeshop from HBL/Rosalina that once, on 11.5, should work as expected.
Thank you and sorry for bothering but sometimes I feel overwhelmed from all this informations and not having followed the 3DS scene for some years only made this worse.

OK, if you don't plan to link NANDs, it should be fine to just update via System Settings. And FBI, Freeshop, and CIAngel should already be ready to use in Rosalina's homebrew menu. So, just FBI (as a CIA) and JKSM need to be installed.

Also, its not that complicated updating an EmuNAND to 11.2. Just use the latest 3DNUS to grab 11.2 and use SysUpdater to update it.

 

[onnihs]

Thank you very much! Successfully updated to 11.5 on sysnand and gw emunand working properly.
Just the last question: to eventually update b9s, I should replace old safeb9sinstaller.firm on b9s/payloads with the updated one, boot while holding down (CBM9) and run safeb9sinstaller and once it finishes use lumaupdater from sysnand to update luma correct?

 

[Kazuma77]

Thank you very much! Successfully updated to 11.5 on sysnand and gw emunand working properly.
Just the last question: to eventually update b9s, I should replace old safeb9sinstaller.firm on b9s/payloads with the updated one, boot while holding down (CBM9) and run safeb9sinstaller and once it finishes use lumaupdater from sysnand to update luma correct?

You would place the new "boot9strap.firm" and "boot9strap.firm.sha" in the "boot9strap" folder and then just run the installer from the down menu as you described. It is unlikely that Safe B9S Installer itself will be needing any updates. Unlike with A9LH, the method of installing B9S is unlikely to change. It's pretty much a straight backup, verify, and copy process (that's why it was so easy to have a script replicate it's functions).

I'm not sure how the updater works. I prefer to do it manually. It may just find the running copy. But that's probably OK for the most part. The main one (as far as the scripts are concerned) is always going to be the "Luma3DS.firm" in "b9s/payloads" though. If you ever change a hotkey, the default payload, or switch chainloaders, the scripts that do it all use the files in that folder. So you can always update the other copies as needed by changing the default payload (if Luma's the default) and/or hotkey the old copy is on (if you're using the defaults, just hold R at boot, since to restore the defaults, it copies the payloads from "b9s/payloads" after all). For reference, the other 3 copies are "boot9select/default.firm", "boot9select/a.firm", and "legacy/payloads_legacy/y_.firm". You could also just copy the one that gets updated back to the PC, to the "Updater" folder as "Luma3DS.firm", run the updater, and copy the configuration back, though that sort of defeats the whole "less trips to the PC" mantra.

 

[mdg]

Hello Kazuma77

I have got a question lately i updated my SysNAND to 11.5 and a EmuNAND 11.2 for use with gateway as i still like the use of .3ds and the cheat support. But i notice when I download any games from Freeshop, once the games have installed i got to unwrap them and the game icons show up on my SysNAND home screen. Then when I boot into EmuNAND the new games i downloaded on my SysNAND are not showing up on my EmuNAND. But once I finished with my EmuNAND and boot back into SysNAND for some reason the new games i downloaded i got to unwrap them again. My question is, is there a way whatever i install on my SysNAND to show up on my EmuNAND vice versa?

Thanks on any help

 

[Kazuma77]

Hello Kazuma77

I have got a question lately i updated my SysNAND to 11.5 and a EmuNAND 11.2 for use with gateway as i still like the use of .3ds and the cheat support. But i notice when I download any games from Freeshop, once the games have installed i got to unwrap them and the game icons show up on my SysNAND home screen. Then when I boot into EmuNAND the new games i downloaded on my SysNAND are not showing up on my EmuNAND. But once I finished with my EmuNAND and boot back into SysNAND for some reason the new games i downloaded i got to unwrap them again. My question is, is there a way whatever i install on my SysNAND to show up on my EmuNAND vice versa?

Thanks on any help

You simply need to copy "dbs/ticket.db" from SysNAND to EmuNAND. You could do this manually with Godmode9. Or you could use the "Ticket Sync Scripts" in InScripted's "Extra Options" folder. This is exactly what I made them for.

 

[mdg]

You simply need to copy "dbs/ticket.db" from SysNAND to EmuNAND. You could do this manually with Godmode9. Or you could use the "Ticket Sync Scripts" in InScripted's "Extra Options" folder. This is exactly what I made them for.

Can you tell me how this can be done in godmode9 please, Thanks

 

[Kazuma77]

Can you tell me how this can be done in godmode9 please, Thanks

Go to the "1:/dbs" folder, select "ticket.db" and hit Y. Then go to the "4:/dbs" folder, hit Y again, choose the copy option, and enter the combo to confirm.

See? It's not really all that difficult. Still, I include the scripts as a slightly faster way to do it, since they allow you to just pick the option from the GM9 "Scripts" menu. Besides, you know what they say about keeping it simple. Though I guess technically that ship sailed when I added all of those extra features, like configuring your own hotkeys via scripts. But I try to keep things as simple as I can without being an Apple about it (no chronological album order on a $400 device, really?).