You can't since ironfall is not available on eshop anymore.
Moot point, since it has now been updated and Ironhax won't work anymore, but It was still always available if you had previously downloaded it. You just had to go through the re-downloadable software menu.
its not on eshop anymore, but its still downloadable via funky cia... i tried it 1 week ago, both game and update...
See above. funkycia downloads it FROM THE ESHOP in the first place...
OK, I resolved one problem, but I have another: I'm getting the error "Failed to load NATIVE_FIRM: 4".
Looking at the source code, it is because I don't have /rxTools/data/0004013820000002.bin. Except...I do. I also put a copy as 0004013800000002.bin to be safe. And firmware.bin. I also have copies of these three files on the root of my SD card.
I made the file using cdn_firm.py.
I *think* you have this sorted out by now, but first of all, you use firmware.bin made with the .py script for O3DS ONLY. You use the firmware.bin from the reinand package (in the paste bin) and rename it to 0004013800000002orig.bin. Do NOT put copies of them in the root, and do not use all of them at the same time. Remove the ones that aren't for the system you are using and delete rxtools.dat if you are using a 3.0 beta (nightly). rxtools.dat has been replaced with code.bin and is not located in the root anymore.
but pasta with Firmlaunch fixes this. And other temp users agree. Although RxTools doesn't have firmlaunch yet...will It ever?
basically if more games adopt this newer firmware reqirement...Rxtools will be inferior to PastaCFW until this critical feature is brought to Rxtools
What? Of course RxTools uses Firmlaunch! One of the main issues with n3ds is that you can't use devmode (which is using the NAND NATIVE_FIRM instead of firmlaunch).
Sorry for the huge post of quotes. I was even going to quote more, but lost interest. for some reason, I stopped getting notifications for like 10 pages... I finally decided to go ahead and start using an emunand on my N3DS so I could use amiibo with Chibi Robo. It's good to be hard modded. Instead of banging my head over how to update emunand to 9.5 PROPERLY, I simply launched sysnand with an old Pasta build and used sysupdater, then injected it to emunand, then flashed 9.2 back to sysnand.
And by the way, not only is it really recommended to unlink sys/emu NANDs for several reasons, but there is nothing wrong with formatting sysnand on 9.x N3DS even with a downgraded MSET. I don't see what the problem is. Of course, I already had an OOT cart setup to boot back into GW menu to reinstall NVRAM and such (not to mention the retail CN cart)...
I'm not quite sure what the fuss is all about with GBA stuff and supposedly having to install in both emunand and sysnand. That stuff does not require a higher firmware and since both GW and CFW can boot into sysnand, why bother? Just play those games from sysnand and be done with it. EDIT: Strike that about GW. You must be in devmode, unless that patched TWL_FIRM or whatever floating around fixes that. I've never had to deal with it since I own all of those games legit and can simply play from sysnand without any hax or CFW at all.