Hacking [Help] Autoboot RxTools 2.6

  • Thread starter Thread starter Alex3dss
  • Start date Start date
  • Views Views 9,201
  • Replies Replies 63
it's because you got menuhax autoboot in your emunand, this happens when creating emunand with menuhax installed

break it by changing menuhax to boot with a button pressed, ie not type 2, then once booted in emunand change the theme

then boot normal sysnand and unlink nands, see any tutorial

once nands are unlinked you can reinstall menuhax in sysnand to autoboot, type 2

Thx for your answer, i ll try that asap.

Do you confirm it works with rxtools 2.6?
 
I tried diffrent things to boot rxtools 2.6 but didnt work

EDIT:
I tried launching rxtools.3dsx thru ctrbootmanager but also didnt work.
So if rxtools.dat and rxtools.3dsx both dont work then I dont see any other option then downgrading back to 4.5 and use mset again
 
Last edited by Alex3dss,
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.
I found out there is still something wrong here. The original boot.cfg has:

title = ''rxTools'';
path = ''/rxTools/code.bin'';
offset = ''0x12000'';

I guess 0x12000 is for reading a .bin file. I got rxTools.dat which you put in this boot.cfg, but I guess there has to be something changed in offset.
I don't know if you know how you have to do it, but I wouldnt know how the f*ck I have to do that.
 
Hi ! I think I might have a similar problem when booting RxTools. So, I've been able to autoboot to Emunand when i was on the 9.0.2 firmware (on Emunand). I've just done the update to 10.3 (still on Emunand) and now i've got a problem when "Loading the Menu" : The loading screen simply disappear and my O3DS goes back to CtrBoot Screen. On this second boot i've got a crash on a red screen (displayed on the touchscreen). Anyone got an idea ?
 
Hi ! I think I might have a similar problem when booting RxTools. So, I've been able to autoboot to Emunand when i was on the 9.0.2 firmware (on Emunand). I've just done the update to 10.3 (still on Emunand) and now i've got a problem when "Loading the Menu" : The loading screen simply disappear and my O3DS goes back to CtrBoot Screen. On this second boot i've got a crash on a red screen (displayed on the touchscreen). Anyone got an idea ?
what version is your rxtools?
 
Nightly 2015-12-05 i believe. Got it from this tutorial.
Then it should work I guess. Try reinstalling menuhax and all those things. Maybe the problem will be solved then

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

Rxtools 2.6 doesn't autoboot. You need a nightly build of rxtools.
So if I need a new version, how do I update? Which files do I need to add or delete?
 
Then it should work I guess. Try reinstalling menuhax and all those things. Maybe the problem will be solved then

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


So if I need a new version, how do I update? Which files do I need to add or delete?

Look for a nightly build. It contains a folder named RxTools. Copy it to the root of your sdcard. Put the firmware.bin in your sys folder inside the rxtools folder. Rename the firmware.bin if you have N3ds or leave it as it is if you have O3ds.
 
Look for a nightly build. It contains a folder named RxTools. Copy it to the root of your sdcard. Put the firmware.bin in your sys folder inside the rxtools folder. Rename the firmware.bin if you have N3ds or leave it as it is if you have O3ds.
Do I have to remove the old rxtools files? Or the rxtools.dat file?
 
Then it should work I guess. Try reinstalling menuhax and all those things. Maybe the problem will be solved then

I tried to uninstall, reinstall MenuHax but the problem is still there. It's maybe a problem due to the fact that CtrBoot reboots the console each time you go into the settings and close it. I wonder if this "Opening the Menu" window is part of the Settings. Any idea ?

EDIT : Got it !! If you've got the same problem, just hold the button you assigned to bypass the Ctrboot when the "Initializing the menu" popup appears. The console will reboot on the EmuNand. There you got to change the default theme to whatever you like. Power down the console and try the coldboot again. It should work fine.
 
Last edited by Vone,
ok O3ds trying to get ^ this boot direct into Emunand to work BEFORE 10.4 updtae is becoming a pain in my butt ... Citrboot when I attempted this would say arm 9 payload or something near that when I clicked RXtools ... I have used many builds all the same error or if you use themehax I get a black screen once I click it .. I kinda dont want to keep using the web browser due to every link that works to open my emunand REQUIRES WIFI 0.0 annoying ..
 
I tried to uninstall, reinstall MenuHax but the problem is still there. It's maybe a problem due to the fact that CtrBoot reboots the console each time you go into the settings and close it. I wonder if this "Opening the Menu" window is part of the Settings. Any idea ?

EDIT : Got it !! If you've got the same problem, just hold the button you assigned to bypass the Ctrboot when the "Initializing the menu" popup appears. The console will reboot on the EmuNand. There you got to change the default theme to whatever you like. Power down the console and try the coldboot again. It should work fine.
I got 2 questions for you.

1. What the f*ck is a coldboot?
2. Are there maybe different ctrbootmanager's? I never see ''Initializing the menu''
 
Yes. You have to remove the old rxtools folder. You can leave the dat file or delete it. No problem for that.
So I got rxTools 3.0 now. Only one problem. Whenever I start rxtools from ctrbootmanager, the screen goes black (looks like it would load) but it won't go further then the black screen. Any idea how to fix it?
 
So I got rxTools 3.0 now. Only one problem. Whenever I start rxtools from ctrbootmanager, the screen goes black (looks like it would load) but it won't go further then the black screen. Any idea how to fix it?
Coldboot is basically homemenuhax launching a boot.3dsx (because it hijacks the original boot routine and triggers custom code), and CTRBootManager redirects that boot.3dsx to some other CFW/HBL/whatever

@rxTools3.0: Are you sure you generated the /firm/ folder with rxTools.zip/Tools/cdn_firm.py using Python 2.7? You need to copy that /firm/ folder over to SD:/rxTools/sys/<here> or rxTools 3.0 can't boot into EmuNAND (maybe even SysNAND, not sure though)
 
Coldboot is basically homemenuhax launching a boot.3dsx (because it hijacks the original boot routine and triggers custom code), and CTRBootManager redirects that boot.3dsx to some other CFW/HBL/whatever

@rxTools3.0: Are you sure you generated the /firm/ folder with rxTools.zip/Tools/cdn_firm.py using Python 2.7? You need to copy that /firm/ folder over to SD:/rxTools/sys/<here> or rxTools 3.0 can't boot into EmuNAND (maybe even SysNAND, not sure though)
I had a map named Firm and there were 3 files in. But on my sd I had in the rxtools folder a map called data and also had the same 3 files in it
 
I had a map named Firm and there were 3 files in. But on my sd I had in the rxtools folder a map called data and also had the same 3 files in it
I'm not actually sure what a "map" is! Do you have a folder named "firm", and are your 3 .bin files inside of "SD:/rxTools/firm/<the 3 files>.bin"? My only other guess is you had bad luck when trying to boot rxTools: It's not a 100% boot success rate
 

Site & Scene News

Popular threads in this forum