Thanks, found it here.See the Reinand thread in the flashcart section.
Thanks, found it here.See the Reinand thread in the flashcart section.
Thanks!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).
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?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.
used a brand new, freshly downloaded zip with the cfg file, started up bootmanager from HBL, and it's giving me the same problem.No :/
Your boot.cfg config file is corrupted. Copy the one from the archive and start from there once again.
You have to use the latest version of rxTools in order to use it with *hax 2 / CBM.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
that explains it. What're the benefits of updating rxTools? for O3DSXL, that is.You have to use the latest version of rxTools in order to use it with *hax 2 / CBM.
It works with *hax 2 and CBM. Isn't that enough? ^^that explains it. What're the benefits of updating rxTools? for O3DSXL, that is.
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.![]()
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?
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.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.
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.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?)
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.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.
Yes, I also tried with 0.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![]()