Hacking rxTools with Signatures patched out!

  • Thread starter Thread starter AHP_person
  • Start date Start date
  • Views Views 336,503
  • Replies Replies 1,545
  • Likes Likes 44
Status
Not open for further replies.
NOTE: Okay, it appears

Okay, here's how you can do any of this through mset:

1. Pick whether you want to boot a (Gateway-encrypted) Launcher.dat or rxTools.dat and grab the appropriate code.bin - or both.
1a. code.bin for Launcher.dat's: http://s000.tinyupload.com/index.php?file_id=47753777289998764895
1b. code.bin for rxTools: http://filetrip.net/dl?YMiN8kg7dh
2. Put whichever code.bin on the root of your SD card, or grab both and name one something like rxcode.bin and the other gwcode.bin
3. Put the SD card back in the 3DS
4. Clear your 3DS internet browser history and cookies
5. Point your 3DS browser at http://dukesrg.no-ip.org/3ds/rop/?LoadCode4.dat&code.bin (you can change the "&code.bin" part to the name of each code.bin, i.e. &rxcode.bin or &gwcode.bin, I made bookmarks for each)
6. Wait for the browser to crash (should give a "Please save what you were doing and restart" message)

You now have mset installed for whichever thing you want - the rxTools code.bin will launch rxTools.dat, and the Launcher.dat code.bin will launch any Gateway-encrypted launcher.dat (that is, if something gives you a Launcher.dat and a Launcher_GW.dat you're gonna need the Launcher_GW.dat renamed to Launcher.dat)

NOTE: If you followed those tweaks a few pages back to insert the slot0x25KeyX.bin into rxTools.dat, you can't use that modified copy with this, it won't boot. I'm SO glad that was brought up, because otherwise I'd still be puzzling that out, hahah

i put the code.bin on the root for GW, says executing but no crash.

also is there a way to do this without internet?
 
i put the code.bin on the root for GW, says executing but no crash.

also is there a way to do this without internet?

And you used the original link? (i.e. so the name of "code.bin" is correct for what you have on your SD card) Hm. Try rebooting, clearing history/cookies again, and trying again. Out of curiosity, what's your full version number? Like, 4.5.0-10U. If it's below 4.5.0-7 this may not work. However, you should be able to use the "Install NVRAM" option if you can get into the gateway menu via any method, and that should install the launcher.dat mset without any of the code.bin business. Forgot about that.
 
This is great, but I'm having some issues.
I've been using Palatine's CFW up until now, sysnand on 4.2, emunand on 4.2. I converted the rednand to emunand, started rxtools, everything works fine.
I tried to upgrade the emunand to the latest version, but it gives me an error and next time I try to launch the emunand it gives me a black screen. When I try to upgrade through a cartridge, it shows that it succeeded, but the black screen continues.
So the question is
What is the correct way to upgrade the emunand from palatine?
 
OK, i'm stumpped so can someone give me instructions for SYSfw4.5, gatewayfw9.8 method from step 1 to step last and link what's possible to link? I've gone through what I can over and over, but I'm always getting a black screen when booting a gba rom under rx firmware. 3DS boots perfectly fine.

if I have to, i also have a SYSfw9.2 with Cubic Ninja
 
This is great, but I'm having some issues.
I've been using Palatine's CFW up until now, sysnand on 4.2, emunand on 4.2. I converted the rednand to emunand, started rxtools, everything works fine.
I tried to upgrade the emunand to the latest version, but it gives me an error and next time I try to launch the emunand it gives me a black screen. When I try to upgrade through a cartridge, it shows that it succeeded, but the black screen continues.
So the question is
What is the correct way to upgrade the emunand from palatine?
If you successfully booted rxTools after converting your rednand to emunand, it sounds like you did that part properly. Upgrading should be as simple as booting into rxTools emunand and going to System Settings -> Update. Do you have firmware.bin on your SD card?
 
If you successfully booted rxTools after converting your rednand to emunand, it sounds like you did that part properly. Upgrading should be as simple as booting into rxTools emunand and going to System Settings -> Update. Do you have firmware.bin on your SD card?
Yeah, I have all the files, including the 7.0 key. It works fine, but after I upgrade the emunand, either by cart or internet, it gives me a black screen, and I hac to re-inject the backup again. Should I try re-creating an emunand using Gateway Launcher?

EDIT: Nevermind, it booted after trying a second time and leaving it on for a little longer.
 
Yeah, I have all the files, including the 7.0 key. It works fine, but after I upgrade the emunand, either by cart or internet, it gives me a black screen, and I hac to re-inject the backup again. Should I try re-creating an emunand using Gateway Launcher?

EDIT: Nevermind, it booted after trying a second time and leaving it on for a little longer.
Yea, rednand may not work after being updated so try that, make sure to back up sd!
 
Yeah, I have all the files, including the 7.0 key. It works fine, but after I upgrade the emunand, either by cart or internet, it gives me a black screen, and I hac to re-inject the backup again. Should I try re-creating an emunand using Gateway Launcher?

EDIT: Nevermind, it booted after trying a second time and leaving it on for a little longer.

Oh, yeah, sorry, I should've mentioned, the first time you boot into an updated fw it takes a minute or two to "set up the Home Menu" and before that it shows a black screen for ~20 seconds
 
Is there a way to check the region of my cia?
Not without installing it, but if you install it you can open up FBI and search for its ID on http://3ds.essh.co/ . The last letter in the serial (i.e. the P in CTR-BALP/CTR-P-BALP) is usually the region identifier; P for EUR/PAL, E for USA/NTSC, J for Japan, etc.
 
  • Like
Reactions: Adeka
Wish I had the time; I have an idea re: switching between ssb and twl support, a cia that shuffles bet the two rxtools.dat, where you run it every time you need to switch; then reload rxmode.

a simple file rename I think will work
Code:
sdmc_rename(struct _reent *r,
const char *oldName,
const char *newName)
 
Please help me out, I have a O3DS on 4.2 with palantine and a bunch of 3ds and gba (AGB) games installed. I dont really understand this.
1) Will this allow me to play Smash Bros?
2) Will I be able to play Hyrule Warriors when it comes out?
3) Are my old games/saves going to be deleted? What will happen with the GBA ones?
 
Alrighty then, who wants to unpack rxTools and do what they want on their own?

Here are four tools you can use to unpack and repack rxTools.
https://mega.co.nz/#F!Dc8HlRIR!uBhpFbwUWEZ5tRajs-f1lg

rxTools Unpacker:
This tool will decrypt and unpack rxTools for you, and you should get two files: main.dat and filepack.dat.
This utility is drag 'n' drop.

rxTools Packer:
This does the opposite. It will pack and encrypt main.dat and filepack.dat into rxTools.dat.
This utility should be run in the same directory as main.dat and filepack.dat.

filepack Unpacker:
This will unpack filepack.dat, and it should give you four files: file000-003.bin
This utility is drag 'n' drop.

filepack Packer:
This will pack filepack.dat back together.
This utility should be run in the same directory as file000-003.bin

Here are their sources:
rxTools Unpacker: http://pastebin.com/ZWuWc6SV
rxTools Packer: http://pastebin.com/wqEKc7Gi
filepack Unpacker: http://pastebin.com/303DAJ1a
filepack Packer: http://pastebin.com/sfyaRv6X

Extra:

FIRM patches are stored in file002.bin from filepack.dat.

The format of file002.bin is fairly simple:
0x00-0x03: Number of patches.

Directly after are the patches:
0x00-0x03: Offset in FIRM
0x04-0x07: Size of data to write
0x08-0x...: Data to write

If you don't feel like parsing them, they're also here: http://pastebin.com/fazkjHRn

The rxTools splash screen is file003.bin from filepack.dat.
makebgr.bat from here: https://gbatemp.net/threads/release...-x-cfw-with-customizable-boot-options.388071/ does the trick.

Again, thanks to @Apache Thunder for testing.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum