Part of my sticky actually covers this
But basically, CFWs only apply patches to the NAND and are basically only a means of reading the NAND. But you can safely switch and or multi-boot CFWs on the same system. In fact, I am running 5 different CFWs right now on my 3DS and I have never suffered any ill effects from doing so.
As a dev its ok to have 5 (extended testing)
But why the heck do you need 5 CFW's?^^
Because I am one of the Temp's most well known testers and CFW enthusiast.As a dev its ok to have 5 (extended testing)
But why the heck do you need 5 CFW's?^^
how do I multi boot corebink and Luma?Because I am one of the Temp's most well known testers and CFW enthusiast.
I am going to be honest with you and don't take this personally. If you don't know how to do this, Corbenik might not be the CFW for you. Corbenik is not intended for the faint of heart and is intended for powerusers/devs. Still, you can use Luma3DS's chainloader to boot into Corbenik.how do I multi boot corebink and Luma?
what abot Luma and CakesFW?I am going to be honest with you and don't take this personally. If you don't know how to do this, Corbenik might not be the CFW for you. Corbenik is not intended for the faint of heart and is intended for powerusers/devs. Still, you can use Luma3DS's chainloader to boot into Corbenik.
You can just load any CFW like any A9LH payload. You can also load them through external boot managerswhat abot Luma and CakesFW?
so How do I multi boot (where do I place files and stuff like that?)You can just load any CFW like any A9LH payload. You can also load them through external boot managers
Just setup the CFWs like you normally would, then rename the launchers. So say you are going to Luma3DS and Corbenik. You setup your launcher (using Luma3DS as an example) and keeping the Luma3DS launcher named "arm9loaderhax.bin" and renaming the Corbenik launcher from "arm9loaderhax.bin" to let's say "Corbenik.bin"so How do I multi boot (where do I place files and stuff like that?)
ok thanksJust setup the CFWs like you normally would, then rename the launchers. So say you are going to Luma3DS and Corbenik. You setup your launcher (using Luma3DS as an example) and keeping the Luma3DS launcher named "arm9loaderhax.bin" and renaming the Corbenik launcher from "arm9loaderhax.bin" to let's say "Corbenik.bin"
Then you just place that bin file into the "/luma/Payloads". Once there you launch into the payload menu and you can launch Corbenik that way.
wait what is payload menu?Just setup the CFWs like you normally would, then rename the launchers. So say you are going to Luma3DS and Corbenik. You setup your launcher (using Luma3DS as an example) and keeping the Luma3DS launcher named "arm9loaderhax.bin" and renaming the Corbenik launcher from "arm9loaderhax.bin" to let's say "Corbenik.bin"
Then you just place that bin file into the "/luma/Payloads". Once there you launch into the payload menu and you can launch Corbenik that way.
Chainloading, if you hold "Start" while booting the system, you can get into the chainloading menu.ok thanks
wait what is payload menu?
oh that ok thanksChainloading, if you hold "Start" while booting the system, you can get into the chainloading menu.