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).