Homebrew CtrBootManager: 3ds boot manager/loader (HomeMenuHax)

  • Thread starter Thread starter cpasjuste
  • Start date Start date
  • Views Views 405,320
  • Replies Replies 850
  • Likes Likes 96
I finally added editing the configuration from the app itself ! I need to polish one/two things but i should be able to release it tomorrow.
By the way, i also have a very good boot rate with ninjahax 2.5, themehax 2.0 and autobootfix = 8 on old3ds (like some previous reports).
Thanks!

Well i don't have to much problems booting NH2.5 with MH2.0 and autobootfix like it is (1 out of 10 tries fails), but 8 seems nice, gonna try that out 0 /10 would be much better anyway ;)
 
Are you using latest 2.5 hax and is your 3ds old or new ?

After reflexion it can be because :

- You use a modified ftbrony which comes without XML descriptor for additional service ? Try with latest ftbrony from smea starter pack.
- The netloader doesn't handle XML descriptor so I guess it can break some things, I'll take a look.
I've got a N3DS EUR v9.0.0.20, and I'm using ThemeHax v2.0 (which should be the same as Ninhax 2.5). You were right, I have been using a version of ftBrony that I compiled myself from source. I just replaced the .XML file, and now it works, although not always on the first try - meaning I have to close and restart ftBrony (it's the same with HBL, so that's a non-issue). The problems with 3DSlink persist, though. Maybe you can somehow force initializing the service for it?
 
I can't get the config file to work for some reason. I still use the old rxTools (located in root), but Whenever I run the HBL app, I only get"select a file to boot", Netloader, Reboot, and Power Off. When I hit SELECT A FILE and choose RXTOOLS, it just freezes and I have to power down manually. I can't even button-press back to HBL
You have to use the latest version of rxTools in order to use it with *hax 2 / CBM.
 
I

used a brand new, freshly downloaded zip with the cfg file, started up bootmanager from HBL, and it's giving me the same problem. :(

Also "boot.cfg" needs to be at the root of your sdcard.

--------------------- MERGED ---------------------------

I've got a N3DS EUR v9.0.0.20, and I'm using ThemeHax v2.0 (which should be the same as Ninhax 2.5). You were right, I have been using a version of ftBrony that I compiled myself from source. I just replaced the .XML file, and now it works, although not always on the first try - meaning I have to close and restart ftBrony (it's the same with HBL, so that's a non-issue). The problems with 3DSlink persist, though. Maybe you can somehow force initializing the service for it?

Does it hang at 100% ? I just noticed that I seems to have broke netloading once more time in latest version (but it should receive the file and hang at 100% just before launching it. I'm investigating).
 
  • Like
Reactions: AileenLumina
Does it hang at 100% ? I just noticed that I seems to have broke netloading once more time in latest version (but it should receive the file and hang at 100% just before launching it. I'm investigating).
No, I get two error messages and it wouldn't even display an IP. I think the problem is that it doesn't get a WiFi connection.
 
@cpasjuste This boot.cfg hereby applies to be the new default boot.cfg. (Edit it as you wish, just a suggestion)

// Boot menu configuration
boot_config =
{
// Default timeout in seconds
// if timeout = 0 (autoboot without delay)
// if timeout = 3 (autoboot after delay of 3 seconds)
// If timeout = -1 (disable autoboot)
timeout = 0;


// delay for timeout = 0 (not in seconds)
// use 2 for new 3DS, 8 for old 3DS
autobootfix = 2;

// recovery key if timeout = 0
// hold this key after turning on the 3DS to enter the menu
// keycode list : https://goo.gl/4XLDIL
recovery = 2; // SELECT

// Default boot entry for autoboot (starts counting at 0, not at 1)
default = 0;

// Boot menu entries (11 max)
entries =
(
{
title = "emuNAND (rxTools)";
path = "/rxTools/sys/code.bin";
offset = "0x12000";
},
{
title = "sysNAND (PastaCFW)";
path = "/3ds/PastaCFW/PastaCFW.3dsx";
offset = "0x12000"
}
);
};

Edit: thx to autobootfix = 2, my n3DS now always (yes, ALWAYS) boots rxTools successfully.
 
Last edited by AileenLumina,
No, I get two error messages and it wouldn't even display an IP. I think the problem is that it doesn't get a WiFi connection.

Yes this is the problem, that's a really weird one though. If you launch it from homemenu then you launch it from sysnand I guess, so you have a working WiFi connection setup on sysnand ? If you replace CBM boot.3dsx with HBL one then WiFi is OK ? (Still on sysnand?) Also note that you need to wait a few seconds before WiFi is up and get rid of the two errors (which I sometime have if I go to fast). But well I guess you know/tested all this already.
 
Last edited by cpasjuste,
  • Like
Reactions: d0k3
Yes this is the problem, that's a really weird one though. If you launch it from homemenu then you launch it from sysnand I guess, so you have a working WiFi connection setup on sysnand ? If you replace CBM boot.3dsx with HBL one then WiFi is OK ? (Still on sysnand?)
Yup, that's correct. HBL seems to handle WiFi connection differently though. It will attempt to connect right after it started. At least @mashers grid launcher shows that via a WiFi signal indicator.
 
Hi,

I'v uploaded a new version (b09) which does :

b09: add simple boot configuration screen ("More... -> Settings" menu)
b09: (re-re-re-re) fix netloading code

Sorry d0k3, this won't fix your problem tough :/
 
  • Like
Reactions: Keizel
By the way, i think we don't need the "autobootfix" anymore as a value of "0" seems to work fine too (at least on o3ds).
 
By the way, i think we don't need the "autobootfix" anymore as a value of "0" seems to work fine too (at least on o3ds).
I'm really sure about that "autobootfix = 2" is better than "autobootfix = 0" on n3DS because since I use the value 2, my boot success rate increased from 90% to 100%. I booted my n3DS now about 25 times and it didn't fail a single time.
 
I'm really sure about that "autobootfix = 2" is better than "autobootfix = 0" on n3DS because since I use the value 2, my boot success rate increased from 90% to 100%. I booted my n3DS now about 25 times and it didn't fail a single time.

I think it may just be a coincidence. So you mean you also tried with "0" ? Could you do the test(s) again for me :D
 
I think it may just be a coincidence. So you mean you also tried with "0" ? Could you do the test(s) again for me :D
Yes, I also tried with 0. :)
No problem, I will boot 25 times into rxTools using 0 and 25 times using 2, then I'll report the stats.
 

Site & Scene News

Popular threads in this forum