GodMode9 v1.3.1

Yes, I derped. The last release broke the very important FAT mount feature, effectively leading to certain stuff in a certain guide no more working. Sorry!

This wouldn't be GodMode9 if I wouldn't at least give you a new goody that makes the update worthwhile for you. This is new:

• Fixed the broken FAT image mount feature
• ISO 8601 standard used for date&time
• Brightness is changeable via the volume slider, courtesy of @Wolfvak, with some additions by @al3x10m

Thanks everyone (all five of you, lol) who opened up an issue and pointed out this issue to me. Everyone please update, have fun.

GodMode9 v1.3.0

New release already, with some much wanted features. This is new:

• RTC clock support - that means (among other stuff) correct dates for FAT file modifications. Be sure to read the updated quick start guide below.
• New DATESTAMP / TIMESTAMP variables for scripting (see HelloScript.gm9, also take note of the changed NAND backup scripts).
• Chainloading FIRMs - big thanks go to @Wolfvak, who did all the heavy lifting. The option for this is in the A button menu.
• Independent FIRM - this means GM9 can now run out of the FIRM0/FIRM1 partition. Don't do this if you don't know exactly what you're doing. Thanks for this go to @Wolfvak, again.
• You can now create dummy files of any size via R+Y.
• The usual batch of smaller fixes and improvements.

Big thanks for this release go to @Wolfvak, who made this possible, also @al3x10m, who again did a tremendous amount of testing. The RTC clock feature was, again, made possible by @profi200, with some help from RTChanger author @Storm-Eagle20. Thanks to all of you!

Important hint (1): As stated in the previous release, this release removes all entrypoints other than FIRM. Use an older release if you really have to use this from a pre-sighax entrypoint.

Important hint (2): As I get asked about what requirements an aeskeydb.bin file has to fullfil a lot, a perfect one can be found somewhere on the net, is exactly 1024 byte big and has an MD5 of A5B28945A7C051D7A0CD18AF0E580D1B. Have fun hunting! Also note that on a boot9strapped system this is purely optional.

Important hint (3): Starting with this release, it is recommended you properly set up your RTC clock once. Find the option via HOME button -> More.... Also keep in mind that you should fix your system OS clock afterwards.

GodMode9 v1.2.8 (last legacy release)

A special release of GodMode9 this time (we'll get to that below). This is new:

• New input, decrypt, encrypt, buildcia commands for scripting
• New CURRDIR environment variable for scripting
• Fix case sensitive write permission checking (critical!)
• Fix bad line numbers in text viewer
• Fix TWL key init on certain A9LH entrypoints
• Miscelaneous smaller fixes and improvements

Everyone should update their GodMode9 installation because of the critical bugfix. That critical fix fixes some cases where write permissions were not checked properly (don't worry, this was still an edge case, you'd have to trigger it yourself via reckless decisions and noone I know of is affected).

Now, this is the last legacy release, meaning, starting from this release, all entrypoints older than A9LH will be removed from the source code. That includes Brahma, GW and all CakeHax variants. This is also the reason this release archive contains compiled entrypoints. Most (= basically all) users will just need GodMode9.firm. If you have still relied on these old eps up till now, finally get your hacking up to date (gdi!). Refer to The Guide.

GodMode9 v1.2.7

A new GodMode9 release, the star feature of this being scripting support. This is new:

• Support for running .gm9 scripts (take a look at HelloScript.gm9 to learn how it works)
• New viewer for text files (views .gm9 scripts, too, of course)
• Simplified EmuNAND / RedNAND creation options
• Safety confirmation on copy / move / inject user cancels
• Nagscreen for embedded backup if it is not found
• Numerous bug fixes and improvements, actually too many to list here.

Scripting allows you to automate and simplify things. With the script menu inside the HOME menu it is now also possible to replicate D9 functionality in a similar menu structure (if you think that's worth the work...). A sample script and two NAND backup scripts are already included, here's some more [link removed] for you to have a look at (only run if you actually understand what they do).

Release notes

• The standard output path is now 0:/gm9/out, and the recommended path for support files is 0:/gm9/support.
• You may miss the NAND backup function in the HOME menu - that's now found inside the Scripts... menu after a proper setup (hint: see Quick Start Guide).
• An embedded essential backup is highly recommended (see S:/essential.exefs once you have it). Either make one, or suffer through the nag screen every GM9 boot.
• Entrypoints older than A9LH are no more included in the release archive (you may not even notice, but if you do, install b9s, goddammit).

Quick start guide

These short instructions apply to all users who have ARM9loaderhax or SigHax and Luma3DS installed (Luma3DS set up with standard paths), which will be the majority of all GodMode9 users. Here's how to set it up quickly:

• [A9LH only] Rename GodMode9.bin(from the release archive) to X_GodMode9.bin(change Xto the button of your choice) and put it into sd:/luma/payloads/
• [SigHax only] Rename GodMode9.firm(from the release archive) to X_GodMode9.firm(change Xto the button of your choice) and put it into sd:/luma/payloads/
• Copy the gm9 folder from the release archive to your SD card. Then, get good versions of aeskeydb.bin, seeddb.bin and encTitlekeys.bin from somewhere (don't ask me!) and put these three files into sd:/gm9/support (optional but recommended for full functionality).
• Helpful hint #1: Go here for step by steps on doing some common tasks in GodMode9. Especially users coming from Decrypt9WIP or Hourglass9 may find this to be helpful.
• Helpful hint #2: Never unlock the red write permission level unless you know exactly what you're doing. You will notice that prompt when it comes up, it features a completely red screen. It is recommended you stay on the yellow permission level or below at all times to be completely safe. Also read more on the write permissions system below.

You may now run GodMode9 via holding the X Button (or any other button you chose) at startup.

GodMode9 v1.2.1

A new release with a very important fix, sighax / b9s users - please update. This is new:

• Reduced the N3DS ram drive size to 64MB (sighax only, cause extended FCRAM is disabled)
• Full support for custom NCSDs (still experimental at this point)
• Added support for upcoming boot9strap and Luma 3DS releases (thanks @TuxSH)
• OTP is now decryptable via GM9 - look for M:/otp_dec.mem
• Essential backup now contains the otp instead of the otp hash
• Support for setting up GW type EmuNANDs
• The usual stash of minor improvements and bugfixes

The last version's ram drive had a bug when running from boot9strap on N3DS, where files on the drive could get corrupted if they are written to a certain portion of memory.

As for custom NCSDs - @ApacheThunder showed us it is possible, and now custom NCSDs are also fully compatible with GM9. Don't try anything stupid if you don't know what you're doing. Maybe do your experiments on EmuNAND first? Also, take note that GM9 can only help in repartitioning, you will need other tools, too.

GodMode9 v1.1.8

A big release to accompany today's big revelation. This is new:

• FIRM entrypoint supported, use GodMode9.firm (chainload via Luma 3DS, thanks @TuxSH & @AuroraWright)
• Ability to dump boot9, boot11 and otp (works via Boot9Strap only, thanks @SciresM)
• New search for installed titles, just use R+A on title dirs (1:/title, 2:/title, A:/title, ....)
• New CXI dumper (use the A button on TMD files)
• Game file renamer included (allows to rename NCCH, NCSD, CIA and NDS files)
• Improved topdown mode is now standard
• Various minor improvements and bugfixes

Starting with this release, you're now able to dump bootrom from the comfort of your home (sighaxed systems only) - but don't forget @SciresM and boot9strap did all the hard work for you. Getting the OTP is no trouble anymore, either, thanks to the magic of sighax.

The new installed title search works similarily to what FBI does, in that it shows you a list of titles installed in your system, and you can dump CXIs or build CIAs right from this list.

GodMode9 v1.1.3

Not much to see here, this is a pure bugfix release. This is new:

• Build the output path for encTitlekeys.bin / decTitlekeys.bin / aeskeydb.bin / seed.bin if it does not exist
• Fix some SD cards not mounting (bug introduced in v0.6.6) - thanks @Linden10 for being a patient tester
• Some even more minor stuff

"But, I want new stuff!"
Alright, I hear you. See here:

This release also contains an experimental alternative build of GodMode9 with the top and bottom screen functionality switched. Happy?

GodMode9 v1.1.2

It's release time again! This is new:

• Title info display for NCCH/NCSD/CIA/TMD/SMDH/NDS
• Decrypting / encrypting / building / mounting aeskeydb.bin
• Decrypting / encrypting / building encTitlekeys.bin / decTitlekeys.bin
• Building seeddb.bin
• Improved essential backup feature, now includes NAND CID & OTP hash
• Increased ramdrive storage size (thanks @Wolfvak)
• Fixed mounting ticket.db (thanks @saibotu)
• Various smaller bugfixes

The new features for encTitlekeys.bin / decTitlekeys.bin / seeddb.bin / aeskeydb.bin are found inside the A button menu. To build encTitlekeys.bin / decTitlekeys.bin / aeskeydb.bin, select / mark (with L) one or more compatible files (tickets, ticket.db, slot??Key?.bin, ...). There's a also a new entry in the HOME menu, allowing to build multiple support files at once.

Starting with this release, GodMode9 is on par with Decrypt9WIP. Every feature that is in Decrypt9WIP has an improved counterpart in GodMode9 (minor exceptions here).

GodMode9 v1.0.7

A new release already? Yup, on @Plailect's request, cause this has something very important for The Guide. As expected (two days after the last release), the list of changes is rather small.

This is new:

• New, improved CTRNAND transfer method
• A minor bugfix

SafeMode9 users (really, you still want that thing?): Check the last release for info. Or compile yourself. Or let someone compile for you. Whatever.

GodMode9 v1.0.6

A new release to accompany @Plailect's update of the Guide(tm). This is not the big update you came to expect, but this time a rather small one, including mostly minor new features, maintenance and bug fixes.

This is new:

• New fancy splash screen and GodMode9 logo
• CTRtransfer made possible (recommended on A9LH only, refer to the Guide)
• New NAND backup operation in HOME menu
• Easy restore of H&S after injection from HOME menu
• Improved TWL cart compatibility (thanks to @Normmatt)
• Red screen indicates extra dangerous operations now
• Allow setting up the bonus drive even if little space is available
• Improved devkit support for NCCH / CIA operations
• Automatic detection of SD card insert and ejects (you still need to unmount!)
• Dirs can be analyzed (for total size / # of files / # of subdirs) now
• "Copy to 0:/gm9out" operation for dirs is now available
• Images can now be mounted from ram drive and bonus drive

As always, thanks everyone involved in this release, and especially to @Plailect for putting his trust in GodMode9!

And now, something else entirely: Why you don't need SafeMode9.

• First of all, know that, when running software from ARM9, a NAND backup is essential. That goes for everything, for Decrypt9, for Hourglass9, for Luma 3DS, for GodMode9 and for SafeMode9. It's not like these tools are not well tested and considered safe, but doing low level operations in ARM9 software without a NAND backup is considered foolish. You don't even have to keep your NAND backup up to date (you can, of course!), but you're supposed to have one.
• Permission unlock screens only turn up when required, and tell you about possible dangers. These should be paid attention to before unlocking, and that goes for SafeMode9 and GodMode9.
• Now, do you trust yourself to do this? When a completely red screen turns up, telling you about the dangers of unlocking that write permission and asking you to enter that button sequence, press B and do not enter that button sequence unless you know exactly what you're doing. If so, congratulations, you may now use GodMode9 instead of SafeMode9.

The one difference between SafeMode9 and GodMode9 is that SafeMode9 automatically stops before even reaching the screen mentioned under the last bullet point. Accidental entry of unlock sequences is not possible (the probability for that is somewhere in the realm of 0.001%, and that ignores several variables that make it even more improbable to happen, you also have to actually try something stupid to even reach that screen). If you're still convinced you need SafeMode9, alright, I can't stop you, but prepare to be ridiculed by your splash screen.