nightly 173 arm9loaderhax.bin file for those who want/need it. just extract it.
I still think that the end user should have a choice in which CFW to use and just shove Luma down their throats, but based in my experience, when you give a noob more than one option they tend to screw themselves over.
Would've been nice to at least keep the links, just add something like "**SORRY, THIS PAGE IS OUTDATED**" to the top of the page.
N00bs hate outdated pages, and it's nice in case I want to recommend Cakes to someone. Right now I have to distribute my whole cakes folder in a zip because it's a pain to obtain the twl/agbfirmkey.bin (actually the agb is in Plailect's gist, but the twl one has to be generated from a pre-9.3 system). And even then, it'd only work for o3DS, because that's the only console that I own.
If I come across a n3DS owner all I can say is "Get Luma", and personally, I don't like that.
I agree. I just found out. It's been a month since I converted all my units to A9LH. A damn shame.
Actually, it is possible to boot into Cakes with the AGB and TWL files in a separate folder, then copy them over to the "cakes" folder with something like CTRXplorer, then enter System Settings and exit, reboot into Cakes, and then it will decrypt the files because RAM isn't cleared on reboot by default. I mentioned this before (I should keep a copy on a Notepad++ tab so I can just copy and paste), but, still a good trick. Hopefully that helps. Also, if the files are not on "that iso site" I can fix that.
Alternatively, for those preferring 3DNUS, grab 0004013800000002 (O3DS) and/or 0004013820000002 (N3DS) version 24368 without "Pack as .cia" checked. Especially easier for those who have an O3DS and N3DS -- grab the O3DS file first, replace the 0 after the 8 with a 2, hit "Download" again, and you have both. Just rename the numbered file to firmware.bin as usual.
Last edited by Kazuma77,
Actually, those will be created (for AGB and TWL anyway) from the cetk (unless the firmware is already decrypted). If you need a way to generate the firmkey.bin for the CFW itself, maybe boot another CFW like ReiNAND then reboot into Cakes? Never tried it, but in theory it should work.
EDIT: Just tried it. Cakes folder with nothing but cetks and encrypted firmware files (and the "patches" folder of course). Booted ReiNAND, went into System Settings, hit close, booted Cakes. Firmware decrypted, firmkeys generated, everything working. Booting Luma then Cakes should be equally effective. ReiNAND comes with the firmware.bin needed. Luma needs none. Maybe not the ideal trick since it relies on other CFWs, but still, it works.
Besides, it really is hard to argue against having Luma on the system. Even if you don't want to make it your main CFW, it has many unique features you'll probably find useful at some point. I use Luma as my main CFW myself. But I do believe in having options.
Last edited by Kazuma77,
- Joined
- Mar 26, 2016
- Messages
- 1,365
- Trophies
- 1
- Location
- ↑↑↓↓←→←→BA
- Website
- github.com
- XP
- 2,287
- Country
It looks like it's also possible to use this to get the agb_firmkey and twl_firmkey. Boot firmware, rename files, reboot. Nice find.
Yeah, well, I can't take complete credit for it. Someone else here mentioned it before a long time ago. I'm not sure why I remembered that particular post. Guess I just found it interesting.
I can't provide links to copyrighted materials (site rules). I provided the easiest legal method of getting them in the post right above yours (talk about weird timing). If you want something more, make your request on a site that allows it (someone will fill it, may or may not be me).
Last edited by Kazuma77,
Cakes should be self sufficient and not depend in Luma or ReiNAND
Oh, yeah... Didn't see that.
Still fails on decrypting the ARM9 FIRM binary. Probably because it tries to use the >=9.6 keyslot to decrypt a <9.6 firmware? I'm not too clear on what exactly was the problem with 9.6+ emuNAND on N3DS for so long.
Well, that's only if you need the NATIVE_FIRM firmkey.bin file. The other two can be generated via the move/rename trick. You were talking about how it was problematic getting the AGB and TWL firmkey files (especialy TWL for N3DS users). I provided two alternatives -- move/rename, or boot another CFW first. If you just need AGB and TWL firmkeys, you can use the former without another CFW present.
I understand that option two is less than ideal, but I'm not an idealist. I'm a... paid-in-data promoter (the company leaks the game, I show it to people, tell them I got it free, next thing you know they're buying it out of a sense of obligation to make up for the phantom lost sale, sometime I even guilt trip myself into buying it, damn I'm good
). Needless to say, mid-kid's ethics aren't mine. But I still respect his wishes to keep things legit. Besides, it's kind-of a fun little challenge coming up with ways to keep Cakes installable that way. Perfect would be nice, but I'll take what works at the end of the day.I'm not thinking that would be the cause. Long story short, it was an extra layer of encryption on the N3DS. Without the key for it, there was no unscrambling the new firmware. The extra security was part of the N3DS design. An attempt to make it not so easy to hack. To Nintendo's credit, it worked for almost a whole year. It seems unlikely that having an extra key you don't necessarily need would cause an attempt to decrypt an older firmware to fail. Though you could try temporarily renaming the key file, if it's using it, just to see. It all depends on how the app is coded.
If you've got an A9LH system, what you could do is backup your NATIVE_FIRM folder to SD using Godmode9, rename it (put an A at the end or something), install the CIA, go back into Godmode9 and copy NATIVE_FIRM folder to SD again, rename it as well (put a B at the end for example), then rename the the original folder back, and copy it back over to restore the correct NATIVE_FIRM. Technically, the system should be unaffected by you replacing NATIVE_FIRM as long as you're not actually using CTRNAND NATIVE_FIRM, i.e. booting Luma without firmware.bin in place. I just suggested backing the folder up as a precaution. You should be able to restore the current NATIVE_FIRM via CIA. Anyway, once you're done, you should have a decrypted copy of the 9.0 NATIVE_FIRM in your SD card's 00000002B folder (or 20000002B folder if it's an N3DS). As usual, you should make a SysNAND backup first just in case anything goes wrong.
Granted, you shouldn't have to do all that just to decrypt one file. Still, it will get it done.
Last edited by Kazuma77,
I have been trying for weeks to get the latest nightly to work on my A9LH. I want to use the DSi/GBA patches, but doing a clean boot just looks on "patching."
It also says it failed to load firmkey.bin, even though it's same key I am using on my stable build.
It also says it failed to load firmkey.bin, even though it's same key I am using on my stable build.
It fails to load firmware.bin firmkey.bin or agb_firmware.bin/twl_firmware.bin firmkey.bin?
If it is the first one, maybe the firmkey.bin on Plailect guide will work fine for you
Code:
Failed to load the config.
Starting from scratch.
Loading NATIVE_FIRM...
Loaded FIRM
Loaded Firm key
Decrypting FIRM
Decrypting the NCCH
Decrypting the exefs
Saving decrypted FIRM
Loading TWL_FIRM...
Loaded FIRM
Failed to load FIRM key,
will try to create it,
Failed to load CETK
Loading ARB_FIRM...
Failed to load FIRM key,
will try to create it,
Failed to load CETK
loading cakes."Failed to decrypt the CETK
Please make sure the CETK is right."
I am running A9LH, if that makes a difference.
So it's the agb and twl firmkeys
Place the former as agb_firmware.bin/twl_firmware.bin in the cakes folder, and the latter as agb_cetk/twl_cetk.
To decrypt the agb_cetk/twl_cetk from a9lh, a little workaround is:
- Booting sysnand;
- Extracting the SD card;
- Putting both files in the cakes folder;
- Entering system settings and leaving again.
Last edited by Gray_Jack,
Ayyy~ it worked and now DS(i) and GBA works! That needs to written somewhere. Like none of the posts links in the main post mention this and I am pretty sure if they did, it wouldn't have taken weeks of trail and error.
I just did it from the home screen
The OP mentions it in the 'Current nightly additional information:'
That feel when it was there all along. I admit, that was stupid of me for not noticing.
Similar threads
-
-
-
-
-
-
-
@
Veho:
Illinois is working to ban toxic food additives that have been banned for decades in other countries; additives that can be replaced and all those countries still have Skittles and Mountain Dew. Title of the piece: GUBMINT WANTS TO TAKE AWAY YOUR CANDY -
-
@
SylverReZ:
@Veho, Sounds and smells like bullshit. They don't give you cancer, and California should know that. I don't get why they stick labels that say "may or may not cause reproductive harm or cancer".
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
Mame should be two sets one for preservation of everything and one set for people who just want to play and enjoy the old old ganes -
-
-
-
@
SylverReZ:
@Psionic Roshambo, Believe Japan was going to make it legal at some point, according to a Kotaku story.+1
-
@
Psionic Roshambo:
I swear like 99% of arcade games wouldn't even exist these days outside of MAME the arcade machines are old and busted very few ever saw any sort of home conversion
-
-
@
SylverReZ:
@Psionic Roshambo, There's a lot of obscure Japanese arcade titles that are either lost to time or dumped.+1