There's a link in the OP for the proper firmware.bin, also make sure you get the cetk file too
- Joined
- Jan 22, 2015
- Messages
- 535
- Trophies
- 0
- Age
- 43
- Location
- Military base.
- Website
- colorslive.com
- XP
- 640
- Country
-
and the slot0x11key96.bin too.There's a link in the OP for the proper firmware.bin, also make sure you get the cetk file too
Yep, forgot since it's so new... (And I have an o3ds too)
Apparently they do on n3ds. They don't on my o3ds, but you may try. In any case disable the reboot patches for that to wok, as the current ones are sure to block it.
Added to the FAQ.
Re-read my post, you're reiterating exactly what I wrote.Nope, official reinand uses 10.2 now and the mod version by Aurora Wright uses 10.4.
And Cakes uses, well... whatever firmware version you want really.
10.2 - on O3DS - is useless, as NTR supports up to 9.6. (you might as well use 10.4
)https://github.com/44670/BootNTR/blob/7a29e0a6f935b5d0dab82d22c0bf349528e85333/source/main.c#L215
Last edited by Aurora Wright,
Looking at that line, is there really anything that keeps people from just changing the version number to make it boot? Or is there more stuff (home menu heap changes, addresses, etc.) preventing it from working?10.2 - on O3DS - is useless, as NTR supports up to 9.6. (you might as well use 10.4
https://github.com/44670/BootNTR/blob/7a29e0a6f935b5d0dab82d22c0bf349528e85333/source/main.c#L215
You'd need to find the offsets (which I have no idea how to do), and then I guess FIRMs >= 10.4 will be a pain as it seems Nintendo now randomizes the offsets for functions in FIRM, after it's booted (or at least I was told that way). I hope they find a workaround, or the randomization will have to be disabled entirely by cfws.
Find the link in here for N3DS https://github.com/mid-kid/CakesForeveryWan/commit/d79561eb36818c61f595fc2081df0866bb48d6d6
It will be the red one.
@mid-kid
Is there a reason why you chose to rename the firmware download (i.e 0000001B) to firmware.bin? Why not keep the file name original? It's 1 less step to do for the lazy.
Also, would it be safe to implement a NATIVE_FIRM selector as an option for CFWs in general, or would it be a hassle due to the way files, such as save data, is encrypted on different firm versions?
Is there a reason why you chose to rename the firmware download (i.e 0000001B) to firmware.bin? Why not keep the file name original? It's 1 less step to do for the lazy.
Also, would it be safe to implement a NATIVE_FIRM selector as an option for CFWs in general, or would it be a hassle due to the way files, such as save data, is encrypted on different firm versions?
Read the FAQ.
Originally because rxTools used it too and everyone had it under that name. Now because I support a variety of different ones with different names. Someday I'll just scan a directory and let the user pick which version to use.
Okay, so Cakes has supported patching AGB for a while, but, do you see any AGB __patches__ in the menu? No? How is it supposed to do anything without actual patches? (Also I don't yet support the N3DS one, because it's useless right now anyway)
And to all the people asking questions about the nightlies: Please don't use the nightlies if you don't understand what some things do. I support and answer questions exclusively about the stable versions. I'll just explain them once they're stable. Thanks.
Last edited by mid-kid,
Actually I mean the missing AGB_FIRM error. Which I have ignored
No need to be upsed
That can safely be ignored. If cakes doesn't throw an error up your face telling you to do something, it's fine. I just prefer logging it on the bottom screen instead of silently failing. That makes the user know it failed, if the user had the intention to make it load.
Last edited by mid-kid,
Similar threads
