When I try to start up RxTools from Menuhax, it simply doesnt work.
Rxtools 2.6: Emunand 10.3
Sysnand 9.2.0 - 27E
Menuhax version 1
Rxtools 2.6: Emunand 10.3
Sysnand 9.2.0 - 27E
Menuhax version 1
ctrbootmanager??? What the heck is that?Use menuhax 2.0 with ctrbootmanager and a nightly rxTools build.
That should fix it easily.
Thnx I will try. Looks like a lot of workIs a boot manager, it lets you choose what CFW you want to launch on boot:
https://gbatemp.net/threads/ctrbootmanager-3ds-boot-manager-loader-homemenuhax.398383/
But this doesnt work on RxTools 2.6? I dont feel like updating to a nightly build.Actually you only have to:
1)Install menuhax 2.0
2)Rename HBL's boot.3dsx to boot_hb.3dsx
3)Drop ctrbootmanager files in the root of your SD card (boot.3dsx & config.cg)
4)Replace rxTools files for a newer build.
It shouldn't take more than 10 minutes to do everything.
But this doesnt work on RxTools 2.6? I dont feel like updating to a nightly build.
I just readed a thread you mentioned, but I aint that good with editing codes like that. Could you maybe do that part for me?Ctrbootmanager already brings an entry to autoboot a rxTools nightly build.
I have never tried ro autoboot an official release.
You could try creating an entry for rxTools.dat and see if it works, I think it should without any problems.
To create/edit entries just open the config file using notepad in your PC and replece the path for rxTools.dat
// Boot menu configuration
boot_config =
{
// Default timeout in secondes
// If timeout = -1, disable autoboot
timeout = 3;
// Some devices (n3ds?) seems to have
// some timing problems when using timeout=0 (autoboot).
// You may increase this value to improve boot success rate.
// Default delay (8) should be good for o3ds, 2 seems good for n3ds
autobootfix = 8;
// if timeout = 0 (autoboot),
// hold this key to enter the menu
// keycode list : https://goo.gl/4XLDIL
recovery = 2; // SELECT
// Default boot entry
default = 0;
// Boot menu entries (11 max)
entries =
(
{
title = "rxTools";
path = "/rxTools.dat";
offset = "0x12000";
},
{
title = "HomeBrewMenu";
path = "/boot_hb.3dsx";
}
);
};
Have you tried reinstalling everything?Sorry to hijack the topic. I'm positively stumped. I managed to downgrade my N3DS and create an emuNAND, but I just can't get RxTools to boot. I always get a red lower screen and a black upper screen, and I have to hard-reset. I'm pretty sure I'm using the correct firmware bins, correctly named. Any idea of what may be happening?
Thnx for the work m8! I really appreciate it.Create a file named boot.cfg, put this inside:
Code:// Boot menu configuration boot_config = { // Default timeout in secondes // If timeout = -1, disable autoboot timeout = 3; // Some devices (n3ds?) seems to have // some timing problems when using timeout=0 (autoboot). // You may increase this value to improve boot success rate. // Default delay (8) should be good for o3ds, 2 seems good for n3ds autobootfix = 8; // if timeout = 0 (autoboot), // hold this key to enter the menu // keycode list : https://goo.gl/4XLDIL recovery = 2; // SELECT // Default boot entry default = 0; // Boot menu entries (11 max) entries = ( { title = "rxTools"; path = "/rxTools.dat"; offset = "0x12000"; }, { title = "HomeBrewMenu"; path = "/boot_hb.3dsx"; } ); };
--------------------- MERGED ---------------------------
Edited it since it had missing a couple of things.
One question, then Ill try to stop asking XDActually you only have to:
1)Install menuhax 2.0
2)Rename HBL's boot.3dsx to boot_hb.3dsx
3)Drop ctrbootmanager files in the root of your SD card (boot.3dsx & boot.cfg)
4)Replace rxTools files for a newer build.
It shouldn't take more than 10 minutes to do everything.
I have an O3DS XL on 4.5 and want to Autoboot GW. Is it the same process to do this.
I tried it and the ctrbootmanager works. But when I start RxTools, it doesnt work. Ctrbootmanager crashed (I think it couldnt load rxtools.dat but Im not sure)
Sorry to hijack the topic. I'm positively stumped. I managed to downgrade my N3DS and create an emuNAND, but I just can't get RxTools to boot. I always get a red lower screen and a black upper screen, and I have to hard-reset. I'm pretty sure I'm using the correct firmware bins, correctly named. Any idea of what may be happening?
I m in the same boat.
Can't get it to autoboot and the nighty bluid doesn't work properly for me.