@mid-kid:
if I have the decrypted 'firmware.bin' for the New 3DS, how can I crypt it without searching the file all over the web?
Thank you.
Ok, finally I found it. Thank you for the reply.You can't in a way Cakes expects it. There's some essential parts missing in the "decrypted" version. I never thought loading a decrypted firm would be necessary, so I never implemented it.
I won't be adding a way to load a decrypted firm anytime soon, however. You'll just have to search around the web. It's not like the file is particularly rare.
There's nothing essential missing from the decrypted version... Cakes just expects the encrypted one (why?)You can't in a way Cakes expects it. There's some essential parts missing in the "decrypted" version. I never thought loading a decrypted firm would be necessary, so I never implemented it.
I won't be adding a way to load a decrypted firm anytime soon, however. You'll just have to search around the web. It's not like the file is particularly rare.
There's nothing essential missing from the decrypted version... Cakes just expects the encrypted one (why?)
Re-read the OP, it recently got changed:@mid-kid
Is firmkey.bin no longer needed in the latest build? I don't see any reference to it in the latest download.
Thanks I did read it, but I thought this was for for firmware.bin not firmkey, but yeah I see where I went wrong.Re-read the OP, it recently got changed:
"Copy the firmware.bin linked at the bottom of the post to the cakes directory. Do the same with cetk."
The cetk holds the titlekey, which is then used to decrypt the NATIVE_FIRM, so you don't have to hunt down firmkey.bin anymore.
Thanks I did read it, but I thought this was for for firmware.bin not firmkey, but yeah I see where I went wrong.
This process is just for new installs right? If I have it from previous versions all I need to do is place it in the cakes folder correct? And of course I don't need the cetk in this case?
Thanks
Can I use sysupdater with Cakes without bricking?
I think it's probably fair to assume that you haven't set up an emuNAND thenmy CakesFW doesn't have the options to boot into emunand.
my CakesFW doesn't have the options to boot into emunand.
lol, I am 100% sure I setup emunand because I changed from Reinand Rop to Cake ROP.I think it's probably fair to assume that you haven't set up an emuNAND then
Patches are there, and not sure about the right firmware.bin because i thought I had to hunt it down. I got firmware.bin, firmware9.2.bin, and firmware9.5.bin, and I put all three in thereDid you copy the cakes/patches directory? If so, go to "Select patches", and select "Enable emuNAND".
Also, are you sure you have the right firmware.bin from OP?
Confirmed that I copied that folder, but after I launch the ROP and go into select patches, it only has something like disable sig patchDid you copy the cakes/patches directory? If so, go to "Select patches", and select "Enable emuNAND".
Also, are you sure you have the right firmware.bin from OP?
Redownload cakes and copy the whole folder to your SD card, that should fix these issues, also did you follow the part about cetk?Confirmed that I copied that folder, but after I launch the ROP and go into select patches, it only has something like disable sig patch
I use firmkey.bin, that replaces cetk ??Redownload cakes and copy the whole folder to your SD card, that should fix these issues, also did you follow the part about cetk?
If my sysnand is 9.0U, i have to use firmware.bin that corresponds to 9.0U ?Did you copy the cakes/patches directory? If so, go to "Select patches", and select "Enable emuNAND".
Also, are you sure you have the right firmware.bin from OP?
If you have firmkey.bin then you're fine, I was just making sure you had all bases coveredI use firmkey.bin, that replaces cetk ??
Patches are there, and not sure about the right firmware.bin because i thought I had to hunt it down. I got firmware.bin, firmware9.2.bin, and firmware9.5.bin, and I put all three in there
Thanks, firmware9.5.bin is the right one. One more thing: when do we uncheck the "disable sig checks" ?Look in the first post in the thread, under the download button. There's a link for firmware.bin. Download that version.
Unless you have a new 3ds, in which case, remove the firmware.bin, and rename firmware9.5.bin to firmware.bin (assuming the firmware9.5.bin is an encrypted 9.5 n3ds firmware).