Hey bro... since I trust you and your opinion, why this instead of CTR Boot Manager 1.2?
Well, I see you are already a user of Masher's Grid Launcher. The method described in the opening post allows you to include updated shortcuts to any CFW you like into that, or into the original Homebrew Launcher. Apart from that, it is more of an alternative for different needs than an actual Brahma2Loader vs CTR Boot Manager. I, for example, am also using CTR Boot Manager, but only as a backup (timeout = 0, autoboot to Grid Launcher). For that reason, being able to boot into CFWs / other payloads directly from HBL is very helpful. Also (so that this doesn't stay unmentioned), the recent fixes to the Brahma2Loader project should improve the boot rates beyound what was possible before.
I tried using Brahma2Loader_20151125.zip to boot Reinand, and all it says is:
I assume I'm doing something wrong here, but I have no clue what. I have the loader in /3ds/brahma2loader/brahma2loader.3dsx (along with its smdh), and reinand.dat at the root of my SD card, along with the reinand xml/smdh included with brahma2loader in /3ds.
Whoops, I forgot to mention how I was trying to boot it. I'm trying to auto-boot with ctrbootmanager. Is Brahma2loader not compatible with this method?
Edit: Yeah, looks like it needs to be booted from a homebrew menu like the grid launcher. That won't work for what I want, it seems.
Code:
payload: uNAND";@0
maximum size: 0
Loading failed!I assume I'm doing something wrong here, but I have no clue what. I have the loader in /3ds/brahma2loader/brahma2loader.3dsx (along with its smdh), and reinand.dat at the root of my SD card, along with the reinand xml/smdh included with brahma2loader in /3ds.
Whoops, I forgot to mention how I was trying to boot it. I'm trying to auto-boot with ctrbootmanager. Is Brahma2loader not compatible with this method?
Edit: Yeah, looks like it needs to be booted from a homebrew menu like the grid launcher. That won't work for what I want, it seems.
Last edited by daxtsu,
Yeah. that's the problem. CTR Boot Manager doesn't properly process start parameters yet. Only HBL / Grid Launcher (>= *hax 2.5) do that. Compiling and editing the new Brahma2Loader (f.e. to direct-load everything from a self contained .3DSX or to force loading from a specific place) is pretty easy, though.
I got it, thank you! Now to test the boot rate.
Edit 2: Went back to themehax 1.3 instead of Menuhax 2.0, 6/6 boots into Reinand with Brahma2loader so far (so 100%). I'll stop once I hit 20.
So after 20 boots, using themehax 1.3 with *hax 2.5 payload (I can't use Menuhax 2.0, it boots successfully maybe 20-30% of the time, all others to a white or yellow screen, so it's pointless), I had 18 successful boots. The two failure boots were on a black screen (neither of which were themehax 1.3's fault), so that puts the boot rate on my particular N3DS at 90%. Very acceptable.
Last edited by daxtsu,
Thanks a ton! Tests like these are always very helpful! I guess you could even improve the boot rate by trying around with the voodoo loader parameter. On @FONZD particular 3DS, for example, the console fix (that's voodoo paramer 0x1?, use '?' to apply other fixes) for example helps a lot with these blackscreen failures. 90% is already very good, though.
Last edited by d0k3,
I just prefer boot on the homebrew launcher in order to use retroarch emulators and reboot easily with the combo L+R+down+B.
I do not use a lot rxTools.
About Brahma2Loader_20151125.zip: no changes for me and maybe a lower boot rate than your last release.
So, I keep to use Brahma2Loader_20151124.zip
THX A LOT!
Okay, good to know! Lowering the boot rate is not acceptable, so the next release will have the consolefix restored as it was before and the upper screen consolefix as a separate option (meaning the voodoo parameter will receive an additional bit and have a max of 0x3F).
Hi d0k3,
I've just tried 20 times of loading latest nightly build rxTools 3.0 via Themehax 1.3 payload 2.5.
25/11 Brahma2Loader / rxTools XML
0x12000 0x10000 0x1A
1 OK
2 OK
3 KO BLK SCR
4 OK
5 OK
6 OK
7 OK
8 KO BLK SCR
9 OK
10 KO BLK SCR
11 KO BLK SCR
12 KO BLK SCR
13 OK
14 OK
15 OK
16 KO BLK SCR
17 OK
18 KO EMU BLK SCR
19 HBL YLW SCR
20 OK
Do you have 24/11 build on hands? Can you re-post it?
Thanks.
Last edited by thaikhoa,
Thanks for testing! The newest release has the old behaviour (like 24/11) for the consolefix restored, check the opening post! The top screen consolefix is activated via voodoo parameter bit 0b100000.
The latest build is pretty good in terms of loading into rxTools but suffering black top screen issue (it doesn't matter at all)
N3DS XL 9.2
BUILD: 28/11 Brahma2Loader / rxTools XML
0x12000 0x10000 0x1A
1 OK
2 OK
3 OK
4 OK
5 OK
6 OK
7 OK
8 OK
9 KO BLK SCR
10 OK
11 KO BLK SCR
12 OK
13 OK BLK SCR ON TOP
14 OK BLK SCR ON TOP
15 OK
16 OK
17 OK
18 OK
19 OK
20 KO BLK SCR
17/20 successful loaded
Btw, do you know the settings for Decrypt9WIP to load with Brahma2Loader?
Thanks.
Last edited by thaikhoa,
Yeah, that black screen issue... pretty strange, ReiNAND never had that. For Decrypt9WIP, the best voodoo parameter still has to be found (I'm using 0xF), but success rates almost leave no room for improvement for me anyways. You could use "/Decrypt9WIP 0x0 0x0 0xF". Or try with the consolefix.The latest build is pretty good in terms of loading into rxTools but suffering black top screen issue (it doesn't matter at all)
BUILD: 28/11
1 OK
2 OK
3 OK
4 OK
5 OK
6 OK
7 OK
8 OK
9 KO BLK SCR
10 OK
11 KO BLK SCR
12 OK
13 OK BLK SCR ON TOP
14 OK BLK SCR ON TOP
15 OK
16 OK
17 OK
18 OK
19 OK
20 KO BLK SCR
17/20 successful loaded
Btw, do you know the settings for Decrypt9WIP to load with Brahma2Loader?
Thanks.
Last edited by d0k3,
Decrypt9WIP successfully loaded 8/10 using 0x0 0x0 0xF
I think you don't need to improve the successful loading rate if there's no room for improvement. It's pretty good for now.
Thanks for all.
There is always room for improvement unless we have 10/10 succesful bootsDecrypt9WIP successfully loaded 8/10 using 0x0 0x0 0xF
I think you don't need to improve the successful loading rate if there's no room for improvement. It's pretty good for now.
Thanks for all.
. Think of Brahma v1, there were never failed boots with that. A good choice of voodoo parameter also (besides the payload to load) seems to depend on your console (O3DS/N3DS), maybe even on the FW version and maybe even on stuff we don't know of yet. Well, but to be honest I'm currently out of ideas on what other improvements to implement in there still. And an average of 8/10 is good, the 2 failed boots are just a minor inconvenience.
Last edited by d0k3,
I just uploaded a new one, which may or may not improve boot rates further. As for the voodoo parameter, that is included in each and every release now. Which parameter is best depends on the payload (rxTools / Decrypt9 / etc...), on the console (O3DS / N3DS) and maybe even on FW version and further stuff. You need to try yourself. Possibly good ones are 0x3, 0xF and 0x1F, I think.
Last edited by d0k3,
Similar threads
-
- Article
