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.
Just replace 50 with 52 for o3DS and 1F with 21 for n3DS and you should get the newest firmwares. Keep in mind there's no patches for o3DS (yet).
You should also compile the latest Cakes from source, because support was added just yesterday.
Still doesn't fix the firmkey issue, those need to be distributed manually.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.
Still doesn't fix the firmkey issue, those need to be distributed manually.
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.
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.
anyone have firmware.bin of fw 11.0 for cakesfw ?
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.
Oh, yeah... Didn't see that.You're forgetting the -p option.
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.
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 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
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.
lol, the error is pretty damn clear. Check this and this.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
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.
Or you could do it "in-console" by using something like CTRXplorer...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:
This should reboot into cakes, which will then decrypt the cetk.
- Booting sysnand;
- Extracting the SD card;
- Putting both files in the cakes folder;
- Entering system settings and leaving again.
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.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:
This should reboot into cakes, which will then decrypt the cetk.
- Booting sysnand;
- Extracting the SD card;
- Putting both files in the cakes folder;
- Entering system settings and leaving again.
I just did it from the home screenOr you could do it "in-console" by using something like CTRXplorer...
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
That feel when it was there all along. I admit, that was stupid of me for not noticing.The OP mentions it in the 'Current nightly additional information:'