Idk about that... first, it's already ported to *hax 2.x, keep in mind it only works on 9.0-9.2 and if you could launch the launcher with the original brahma on ninjhax 1.1 then yes it should work on brahma 2, if you CAN'T launch it in NH 1.1 then it will not workDoes this mean/ be possible to boot Gateway launcher.dat when Brahma ported to Ninhax2.0/Browserhax/Themehax/Ironhax?
I wonder if it would be possible to add a Ninjhax version detection in, so that we could have one Brahma 3DSX that would first detect the Ninjhax version, then run the appropriate Brahma code. Maybe I'm missing something, but I think it should not be too difficult. The old (Ninjhax 1.x) HB launcher had no arguments when running the main() of a software, the new (Ninjhax 2.0) HB launcher has arguments. So, it should in theory be enough to check the argc parameter.BRAHMA IIActually there was no way to run Brahma on new ~Haxs, and this creates a problem to the ones (like me) who used some ARM9 utilities like Decrypt9, and had to switch to Ninjhax1.1 or using other entrypoints in order to run them.
I've not seen anyone coming out with an alternative so i decided to try porting it to the new "homebrew standards".
I called it Brahma II, and you can follow his development in my GitHub fork:
I'm sure there will be lots of interrogatives, so i'll write here the essential answers.
What it can do:
What it can't do:
- Run every arm9 code that the original Brahma runs
- It still works on system below version 9.3, no new exploits
- Run on ninjhax2, tubehax, ironhax, oot3dhax, smashbroshax, browserhax, themehax
- If you are a CFW user, this might (haven't tested, and not interested) offer a way to auto-launch it at console boot, by using this as boot.3dsx and installing themehax
- It boots with a rate around 80%
I've put it here to launch the idea and maybe improve the development with your help, since i do not have that much time.
- Run on consoles with system over 9.2
Also all the credits goes to Patois, as the creator of BRAHMA.
Brahma2 runs just fine on ninjhax 1.1b so you can just use it as a drop in replacement for brahma. No ninjhax detection needed.I wonder if it would be possible to add a Ninjhax version detection in, so that we could have one Brahma 3DSX that would first detect the Ninjhax version, then run the appropriate Brahma code. Maybe I'm missing something, but I think it should not be too difficult. The old (Ninjhax 1.x) HB launcher had no arguments when running the main() of a software, the new (Ninjhax 2.0) HB launcher has arguments. So, it should in theory be enough to check the argc parameter.
Ninjhax version detection wouldn't be all that interesting for just the menu based Brahma app, but Decrypt9 uses a specialised version of Brahma that runs the ARM9 payload right away, and having just one 3DSX for all would be a great improvement.
Thank you! I already succesfully tried itBrahma2 runs just fine on ninjhax 1.1b so you can just use it as a drop in replacement for brahma. No ninjhax detection needed.

If the question was why you can't run Decrypt9 via Ninjhax on PastaCFW, the answer is, you need to run Ninjhax from SysNAND, without any CFW loaded. PastaCFW has Firmlaunch, which might make it impossibe to properly run in CFW. If you actually meant the Brahma loader that is for devs only to have a convenient way of autorunning ARM9 payloads and to be able to provide that to their userbase.Hi! Thanx for your work! But is there any guide to make this work on N3DS ninjhax 9.2? I tried your Brahmaloader. It doesnt work. Do I have to update my Pasta?

It's already integrated into most CFWs and things that use BrahmaDoes someone have this compiled and can share?
I have tested pasta cfw and it works on 2.5.Does Brahma II still work on *Hax 2.5?
Can I safely update from 1.1b to 2.1 or 2.5 *Hax to boot PastaCFW/rxTools on my 9.0U N3DS?
Pasta has to be configured for firmlaunch. You can turn it back off, but yea, you still need to use sysnand.If the question was why you can't run Decrypt9 via Ninjhax on PastaCFW, the answer is, you need to run Ninjhax from SysNAND, without any CFW loaded. PastaCFW has Firmlaunch, which might make it impossibe to properly run in CFW. If you actually meant the Brahma loader that is for devs only to have a convenient way of autorunning ARM9 payloads and to be able to provide that to their userbase.
I've been using 2.5 to boot rxTools ever since I set it upDoes Brahma II still work on *Hax 2.5?
Can I safely update from 1.1b to 2.1 or 2.5 *Hax to boot PastaCFW/rxTools on my 9.0U N3DS?
Yeah me tooI've been using 2.5 to boot rxTools ever since I set it up![]()