If cakes boots at all then the offset (0x12000) is probably correct... However the voodoo parameter is a variable that you can play with (its the 0x0 part in your entry) off of the top of my head I don't know what numbers do what but they should be in the OP
What is "unstable"? What is the boot rate of 10 attempts? Also keep in mind that there's more than 0x0 and 0xF (there's 13 choices in between those two) just play around with those numbers until it works at its best (8/10 seems to be a fairly average boot rate if you have a look through the thread)
Redownload from the first post (meaning: make sure you have the newest version). The parameters you are using are correct, but I'd suggest you allso use the voodoo paramter. That's: <arg>/Cakes.dat 0x12000 0x0 0x??</arg>. For 0x??, you have to try what works for you. 0xF is a good value for me (N3DS), but for you another value might be better. As I wrote slightly above 0x3, 0xF, 0x1A and 0x1F are good values. You can try otehr values and reach even better boot rates,
.Redownload from the first post (meaning: make sure you have the newest version). The parameters you are using are correct, but I'd suggest you allso use the voodoo paramter. That's: <arg>/Cakes.dat 0x12000 0x0 0x??</arg>. For 0x??, you have to try what works for you. 0xF is a good value for me (N3DS), but for you another value might be better. As I wrote slightly above 0x3, 0xF, 0x1A and 0x1F are good values. You can try otehr values and reach even better boot rates,
EDIT: I see you already solved it
You mean, loading BrahmaLoader from outside of Homebrew Launcher / loading if before the Homebrew Launcher, correct? Yup, there is. You would have to compile a special version of it and either hardcode the payload location or include the payload directly in the loader. Just take a look at 'resources/AppInfo' and what I just wrote becomes a lot clearer.
By latest release you mean 02-12? There was in fact a buggy (= bad boot rates) release online for a few hours (I hoped no one noticed that), but 02-12 should be free of any known bugs.
That error is almost impossible, for two reasons: (1) there is only one small change between the two releases, which can't affect CFWs in that way and (2) once BrahmaLoader has booted you into rxTools / CakesFW, its job is done, and everything else is rxTools / CakesFW responsibility (meaning bugs are also on the CFWs side) :/. You're using voodoo parameter 0x3, correct? Otherwise, if it is 0x1?, then try the new release with 0x3?. if it was 0x3?, try the new release with 0x1?.
Alright, thank you! No idea what's up with that 02-12 release. I did replace the release on the opening post with the 03-12 release now, though, and marked that release stable. It will stay there until there is an improved version.02-12 release is probably a bad compiled one. I did triple check on 02-12 release again, it actually won't boot to emuNAND. Super weired that you said when entering to CFW menu, BrahmanLoader has done its job.
It now works with your new compiled one
THANKS
<shortcut>
<executable>/3ds/Brahma2Loader_20151203_stable/BrahmaLoader.3dsx</executable>
<icon>/3ds/Cakes.smdh</icon>
<arg>/Cakes.dat 0x12000 0x0 0x3</arg>
</shortcut><shortcut>
<executable>/3ds/Brahma2Loader_20151203_stable/BrahmaLoader.3dsx</executable>
<icon>/3ds/rxTools.smdh</icon>
<arg>/rxTools/sys/code.bin 0x12000 0x10000 0x1A</arg>
</shortcut>Problem is, the best parameters may also depend on your console (O3DS / N3DS) and exact FW version, so experimentation may still make sense. From what I've heard so far these look good. In any case, very good boot success rates >= 8/10 should be possible.
Pretty sure the functionality is already there in Brahma2 and BrahmaLoader, you just use them on their own and not as a library
