Hacking [Release] rxTools - Roxas75 3DS Toolkit [fw 2.0 - 9.2]

  • Thread starter Thread starter Roxas75
  • Start date Start date
  • Views Views 3,356,510
  • Replies Replies 19,240
  • Likes Likes 151
Status
Not open for further replies.
I've been using 2.6 so far and it's been working fine however I wanted to try the nightlies for a change while also installing Themehax for convenience. I tried 2 builds from october, one of them was from lavanoid which included all required files and was listed as the most stable one, however the older one (10-2) would always get stuck at the installation data suite phase (only 2 blocks) while the most recent one would boot into the RxMenu but wouldn't boot into Emunand afterwards. Later I tried going back to 2.6 by swapping the old files back but now the old Rxtools wouldn't boot into Emunand either so I used both my SD and Emunand Backups to get it to work again.

My main questions here are:
1. Is it possible that by installing Themehax into my 3DS somehow that messed up with my Emunand and that's why I couldn't boot into it with either version? (I did browserhax into themehax before attempting to test the nightlies btw)

2. About the installation data suite what are the possible reasons for it to fail? I remember that there were quite a bunch of people having problems on it in the past however I can't recall what was the cause of it.
 
I've been using 2.6 so far and it's been working fine however I wanted to try the nightlies for a change while also installing Themehax for convenience. I tried 2 builds from october, one of them was from lavanoid which included all required files and was listed as the most stable one, however the older one (10-2) would always get stuck at the installation data suite phase (only 2 blocks) while the most recent one would boot into the RxMenu but wouldn't boot into Emunand afterwards. Later I tried going back to 2.6 by swapping the old files back but now the old Rxtools wouldn't boot into Emunand either so I used both my SD and Emunand Backups to get it to work again.

My main questions here are:
1. Is it possible that by installing Themehax into my 3DS somehow that messed up with my Emunand and that's why I couldn't boot into it with either version? (I did browserhax into themehax before attempting to test the nightlies btw)

2. About the installation data suite what are the possible reasons for it to fail? I remember that there were quite a bunch of people having problems on it in the past however I can't recall what was the cause of it.
Fallow all readme files in the nightlys and u should be fine
 
The required firmware files are different between versions. On O3DS, you need to run the python script in the tools menu. You should do this every time until the new "stable" release is official. On latest, o3ds has 3 files in a /firm folder. Oct 2... Firmware.bin in the /sys folder.
 
  • Like
Reactions: MelonGx
I did place the files where the readme pointed, however I got the new firmware.bin from direct downloads rather than from the python script so that could be the issue, I'll try that later thanks.
 
I can't get mset to boot. I'm usnig rxinstaller.nds, it's pointing to YS:/rxTools/sys/code.bin, and it's not working.

rxinstaller.bin is launching through my browser correctly, though?
 
I can't get mset to boot. I'm usnig rxinstaller.nds, it's pointing to YS:/rxTools/sys/code.bin, and it's not working.

rxinstaller.bin is launching through my browser correctly, though?
1. You must use the bundled rxInstaller.nds. Both older and newer are NG.
2. You must confirm your SysNAND is 4.1-4.5 / 6.0-6.3 or MSET downgraded 5.0-5.1 / 7.0-9.2. Other versions are unexploitable.
 
I'm using the bundled one with the latest nightly. My sysnand is 7.0 running what I believe was downgraded using 4.1-4.5.
 
Check out your System Setting.
If it has Nintendo Network ID setting, then you haven't downgraded it.
 
Last edited by MelonGx,
I was previously using rxtools 2.6 and I'm upgrading to the nightly which is why mset not working is weirding me out. I'm gonna give it another shot in a little while.

edit: I'm using the new installer, of course.
 
OK.
If it happens on N3DS, then it's a known bug.
But since it's on O3DS, which is pretty rare, your hardware may be a not-so-good one just like a Pokemon with all DV 0 (maximum is 31).
I had an older version working on it before, but I installed the hax 2.5 and homebrew menu over it, now I wanted to try and boot both. I guess I could copy the version from my 2DS (which was the same one)
 
Ah, okay. Setting myself to 6.x DG did it, even though I could swear I'd ahve done 4.x.

I tried that before actually checking signs of what I'd done, though.
 
After upgrading to the newest nightly, I've found that booting in System Settings sometimes takes longer than usual. The screens go to black for a while until the 3DS logo appears, and I'm in System Settings. Also, I couldn't update emunand from 10.1.
 
Ah, okay. Setting myself to 6.x DG did it, even though I could swear I'd ahve done 4.x.

I tried that before actually checking signs of what I'd done, though.
I think that's referring to MSET being the 6.x version, even though your firmware is higher than 6.x. Gateway MSET works on N3DS with 4.5 MSET, but I think the MSET exploit for rxtools needs MSET 6.x to work above a 4.x sysnand...

This is why I only use MSET on my N3DS for Gateway, and just use menuhax+ctrbootmanager for rxtools.
 
Last edited by urherenow,
I updated my Zelda theme with the last changes, have a look:

w1e61z.jpg

- Theme Thread -

But I have a question, anybody know if the 3D UI Top screen is broken with last builds ?
 
Last edited by FONZD,
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum