Black Cat Special Edition

Special Thanks to @aspargas2 for these changes:

• A safety feature that searches everywhere I could think of on the SD and locations in NAND for the system's OTP, and if it finds it it'll use software AES to encrypt the target firm and write it to firm0 regardless of what was in there to begin with. I have dubbed this "safe mode".
• If the OTP is not found, then instead of doing the traditional XOR attack, it will modify the system's NAND header to create 5 firm partitions, each only 0x200 bytes big, and all within the region of NAND that firm0 would usually occupy. (It leaves firm1 untouched in doing this, so technically the system has 6 firm partitions in this state). It then does the known-plaintext attack 5 times, trying to write a minimal, 0x200-byte firm payload to each of the firm partitions. This lets it get 5 guesses at the current contents of firm0. But because only a 0x200 byte subsection of the firm needs to match with our guess, we can actually support very large ranges of firms at once. Specifically, the attached build should be able to use the XOR attack to install b9s over any native firm 3.0 or newer, any release boot9strap version, any release Fastboot3DS version other than 1.0, and any release Luma3DS version up to 11.0. Really, only native firm should need to be in this list because any system that has already been touched by sighax will hopefully have an OTP dumped somewhere and trigger the safe install. XOR support for other firms is just a "because I could" thing that will hopefully never be used.
• In both of these cases, a custom build of safeb9sinstaller is chainloaded to cleanly install boot9strap to both firm partitions, not just firm0.
• The old special handling for a9lh systems has been removed entirely; it is now handled fine in regular XOR mode.
• b9stool now builds with -Wall -Wextra -Wpedantic -Werror, and I have done some tweaking to the build_headers.py script to hopefully make it less frustrating to use going forward.

To summarize the benefits of this over current b9stool:

• No risk of something going wrong when running b9stool with CFW already installed, as long as OTP is found
• One b9stool version supports almost all native firm versions, and is unlikely to need to be updated in the event of a native firm update
• Users can safely use b9stool on a9lh, and don't have to do anything weird with launching it twice
• The system is left with boot9strap in both firm partitions instead of just firm0, which is good for a few reasons
• Less copyright violation I guess, as only a 0x200 block from native firm needs to be embedded. There are now also some boot9 keys though.

EOL Means End Of Luck Edition

ONLY use with firmware 11.16.0-XX!!
ONLY use with firmware 11.16.0-XX!!
ONLY use with firmware 11.16.0-XX!!

• Updated firms for 11.16
• Updated boot9strap to 1.4
• Workaround a new malloc bug (mallocs in sub-main functions fail to allocate)

Hopefully EOL Edition

ONLY use with firmware 11.15.0-47!!
ONLY use with firmware 11.15.0-47!!
ONLY use with firmware 11.15.0-47!!

Safety Edition

This release provides extra protection for users that might have a lingering a9lh cfw installation and are not aware of it (thanks to @aspargas2 for the new feature!).

ONLY use with firmware 11.13.0-45!!
ONLY use with firmware 11.13.0-45!!
ONLY use with firmware 11.13.0-45!!

For Firmware 11.13.0-45 ONLY Edition

ONLY use with firmware 11.13.0-45!!
ONLY use with firmware 11.13.0-45!!
ONLY use with firmware 11.13.0-45!!

For Firmware 11.10.0-43 or 11.11.0-43 ONLY Edition

ONLY use with firmware 11.10.0-43 or 11.11.0-43!!

Stealth 3-20-19: Update a9lh warning url
Stealth 5-31-19: Another firmware text update
Stealth 8-29-19: Add 11.11 to firmware text

Click the "▷Assets 3" link below to make the download zip appear.